scanning-samples-with-yara
Uses YARA to classify and triage samples at scale: applying rule sets, reading
v1.0.03 instalaciones+3 en 7 días24 EstrellasApache-2.0sincronizado hace 10 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/scanning-samples-with-yaraEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquete794d25cf…35d30a65
794d25cf5bd8…899e35d30a654 archivos · 3.2 KBEscaneoMedio2 hallazgos
- Script ejecutable incluido con la skillscripts/analyst.py
- Enlaces a dominios externos
Fuentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/scanning-samples-with-yara@da7600a
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
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).
Archivos de esta versión
references/11.2 KB
- api-reference.md1.2 KB
scripts/12.6 KB
- analyst.py2.6 KB
- LICENSE340 B
- SKILL.md3.2 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | No | No |
| Ejecuta comandos de shell | Sí | Sí |
| Usa la red | Sí | Sí |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
- MediaArchivo · Script ejecutable incluido con la skillscripts/analyst.py
- InfoEnlace · Enlaces a dominios externos
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v1.0.0 | 13 nov 2026 | da7600a | 794d25cf | Firmada | – |
Más de meltedinhex
Todo de este publicador- 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
Más en Análisis de malware y ransomware
Ver la categoría- 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
Pregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login