Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
meltedinhex/scanning-samples-with-yaraAnálisis de malware y ransomware

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-yara

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
n4bXNoXBtu…OeJtmnBw==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete794d25cf…35d30a65
794d25cf5bd8…899e35d30a654 archivos · ⁦3.2 KB⁩
EscaneoMedio2 hallazgos
  • Script ejecutable incluido con la skillscripts/analyst.py
  • Enlaces a dominios externos
Ver el escaneo completo
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.

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

  • yara CLI or yara-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

bash
python scripts/analyst.py scan rules/ sample.bin
# prints matched rule names, tags, and matched strings with offsets

The 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

bash
python scripts/analyst.py scan rules/ ./samples --recursive --summary

Rank 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-python agree).
  • 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.md for the scanner tool.
  • YARA and yara-python documentation (linked in frontmatter).

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellSíSí
Usa la redSíSí
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

  1. MediaArchivo · Script ejecutable incluido con la skillscripts/analyst.py
  2. InfoEnlace · Enlaces a dominios externos

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v1.0.013 nov 2026da7600a794d25cfFirmada–

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. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login