writing-yara-rules-from-reversed-code
Turns reverse-engineering findings into durable YARA detections: selecting stable
v1.0.04 installs+4 in 7 days24 StarsApache-2.0synced 10 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/writing-yara-rules-from-reversed-codeWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package9590220a…4fe6e79b
9590220a6383…e9244fe6e79b4 files · 3.2 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/writing-yara-rules-from-reversed-code@da7600a
On this page
When to Use
- You finished reversing a sample/family and want a detection that survives recompilation and cosmetic changes.
- You need byte-pattern signatures from decryptors, API-hash constants, or unique algorithms rather than fragile strings.
- You are converting RE notes into hunting/scanning rules for a corpus.
Do not use volatile artifacts (file paths, mutex names that change per build, packer stubs shared across unrelated families) as your primary anchor — they cause drift and false hits.
Prerequisites
- The
yaraengine (and ideallyyara-python) for testing. - A small corpus: target samples (true positives) and clean/unrelated files (false-positive control).
Workflow
Step 1: Choose stable anchors
Prefer, in order: a unique algorithm's opcode sequence (decryptor, hashing loop), embedded magic constants (API hashes, XOR keys, S-box), then distinctive strings only if intrinsic.
Step 2: Extract byte patterns with wildcards
Pull the relevant opcodes and wildcard volatile operands (addresses, immediates) so the rule survives relocation/recompilation:
$dec = { 8A 04 ?? 34 ?? 88 04 ?? 41 3B ?? 7? ?? } ; xor-decrypt loop, regs/disp wildcardedStep 3: Assemble the rule
Combine 2–3 independent anchors with a condition requiring enough of them, plus a cheap
prefilter (file size, PE magic) to keep scanning fast:
python scripts/analyst.py scaffold --name family_xyz --hash 0xABCDEF12Step 4: Validate against the corpus
Run the rule across true positives and the clean control set; require all TPs match and zero FPs on the control.
yara -r rules/family_xyz.yar ./corpusStep 5: Tune and document
Adjust thresholds, add meta (author, date, reference, hash), and record which construct each
string anchors so future analysts can maintain it.
Validation
- Rule matches all intended samples and produces zero hits on the clean control set.
- Anchors map to intrinsic code/constants, not build-specific noise.
metadocuments source samples and the reasoning for each pattern.
Pitfalls
- Wildcarding too little (brittle) or too much (false positives); wildcard only volatile bytes.
- Anchoring on shared library/packer code present in unrelated binaries.
- Skipping the clean-corpus test, shipping a noisy rule.
References
- See
references/api-reference.mdfor the rule scaffolder. - YARA documentation and style guide (linked in frontmatter).
Files in this version
references/11.2 KB
- api-reference.md1.2 KB
scripts/12.1 KB
- analyst.py2.1 KB
- LICENSE340 B
- SKILL.md3.3 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumFile · Executable script shipped with the skillscripts/analyst.py
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v1.0.0 | Nov 13, 2026 | da7600a | 9590220a | Signed | – |
More from meltedinhex
All from this publisher- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
- writing-a-malware-analysis-reportmeltedinhex/writing-a-malware-analysis-report3
More in Malware and ransomware analysis
See the category- yara-sigsdariushoule/yara-sigs4
- monitoring-darkweb-sourcesmukul975/monitoring-darkweb-sources3
- deploying-ransomware-canary-filesmukul975/deploying-ransomware-canary-files3
- implementing-honeypot-for-ransomware-detectionmukul975/implementing-honeypot-for-ransomware-detection3
- yaraaeondave/yara3
- testing-ransomware-recovery-proceduresmukul975/testing-ransomware-recovery-procedures3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login