scanning-samples-with-yara
Uses YARA to classify and triage samples at scale: applying rule sets, reading
v1.0.03 installazioni+3 in 7 giorni24 StelleApache-2.0sincronizzato 10 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/scanning-samples-with-yaraScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto794d25cf…35d30a65
794d25cf5bd8…899e35d30a654 file · 3.2 KBScansioneMedio2 segnalazioni
- Script eseguibile incluso nella skillscripts/analyst.py
- Link a domini esterni
Sorgentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/scanning-samples-with-yara@da7600a
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
When to Use
- You want to classify one or many samples against known malware-family or capability rules.
- You need to confirm a family hypothesis with a targeted rule and read which strings matched.
- You are triaging a directory of files and want to flag the suspicious ones.
Do not use a YARA match as proof of family attribution on its own — public rules vary in quality and can over-match. Corroborate with behavior or code analysis.
Prerequisites
yaraCLI oryara-python(pip install yara-python).- A curated rule set (your own plus vetted public rules). Avoid blindly merging large noisy collections.
- Samples in neutralized form inside the lab.
Workflow
Step 1: Organize rules
Keep rules in categories (family, capability, packer, anomaly) and compile them once for speed. Tag rules so matches are self-describing.
Step 2: Scan and read matches
python scripts/analyst.py scan rules/ sample.bin
# prints matched rule names, tags, and matched strings with offsetsThe matched string offsets matter: they tell you where in the file the signal is (header, overlay, resource), which guides deeper analysis.
Step 3: Triage a directory
python scripts/analyst.py scan rules/ ./samples --recursive --summaryRank files by number/severity of matches to prioritize analyst time.
Step 4: Tune for false positives
If a rule fires on benign files, tighten it: require multiple strings (2 of ($a*)),
anchor to file structure (uint16(0) == 0x5A4D), or raise the condition specificity.
Step 5: Promote good signals to detection
A rule that reliably identifies a family or capability becomes a hunting/detection artifact — hand it to the detection-engineering workflow.
Validation
- Matches reproduce across runs and tools (CLI and
yara-pythonagree). - Each kept rule has an acceptable false-positive rate against a known-clean corpus.
- Match offsets correspond to meaningful file regions, not incidental byte coincidences.
Pitfalls
- Merging huge public rule packs without curation — noise and false positives explode.
- Writing rules on packed bytes that change with every build; prefer unpacked or structural features.
- Over-broad strings (common library text) that match unrelated software.
References
- See
references/api-reference.mdfor the scanner tool. - YARA and yara-python documentation (linked in frontmatter).
File di questa versione
references/11.2 KB
- api-reference.md1.2 KB
scripts/12.6 KB
- analyst.py2.6 KB
- LICENSE340 B
- SKILL.md3.2 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | Sì | Sì |
| Usa la rete | Sì | Sì |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- MediaFile · Script eseguibile incluso nella skillscripts/analyst.py
- InfoLink · Link a domini esterni
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v1.0.0 | 13 nov 2026 | da7600a | 794d25cf | Firmata | – |
Altro da meltedinhex
Tutto da questo editore- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- 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
Altro in Analisi di malware e ransomware
Vai alla categoria- 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
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login