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/triaging-an-unknown-sampleAnálisis de malware y ransomware

triaging-an-unknown-sample

⁨Performs fast first-pass triage of an unknown file to decide depth of analysis:⁩

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/triaging-an-unknown-sample

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

FirmaFirmado, ed25519
YCBSDmdKgL…FGr8fqDQ==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquetef1473edb…4aef2477
f1473edbe30d…94134aef24774 archivos · ⁦4.3 KB⁩
EscaneoMedio3 hallazgos
  • Script ejecutable incluido con la skillscripts/analyst.py
  • command.base64_execscripts/analyst.py:33
  • Enlaces a dominios externos
Ver el escaneo completo
Fuentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/triaging-an-unknown-sample@da7600a

Esta entrada todavía no está escrita en tu idioma, así que aparece en English.

When to Use

  • A suspicious file has arrived and you need to quickly decide whether it warrants deep static/dynamic analysis or can be dismissed.
  • You want a structured first-pass record (type, hashes, packing, notable strings) before committing analyst time.
  • You are batch-triaging many files and need to rank them by suspicion.

Do not use triage results as a final verdict. A clean string review or unknown reputation does not mean benign; it means proceed to deeper analysis.

Prerequisites

  • file (libmagic) for type identification, or the bundled magic-based detection.
  • Optional VirusTotal API key for reputation (hash lookups only — never upload someone else's data without authorization).
  • The sample in a neutralized, non-executable form inside the lab.

Safety & Handling

  • Triage is static: read bytes, never execute. Keep the sample with a neutralized extension.
  • Submit only the hash to reputation services unless you have authorization to upload the file itself; uploads can expose sensitive or attributable data.

Workflow

Step 1: Identify the true file type

Do not trust the extension. Identify by magic bytes:

bash
python scripts/analyst.py triage sample.bin
# reports: detected type, magic, hashes, entropy, suspicious strings

A .pdf that is really a PE, or a .jpg that is a script, is itself a finding.

Step 2: Hash and check reputation

Compute the SHA-256 and look it up (hash-only) to see if it is known:

bash
python scripts/analyst.py reputation --sha256 <sha256> --vt-key $VT_API_KEY

Known-bad with many detections → escalate. Unknown → continue triage; absence of detections is not exoneration.

Step 3: Estimate packing via entropy

High, uniform entropy across the whole file or a code section suggests packing or encryption:

text
entropy ~7.9 / 8.0 over most of the file  -> likely packed/encrypted
mixed entropy with readable strings       -> likely unpacked

Step 4: Skim strings for quick signal

Look for URLs, IPs, registry paths, suspicious API names, and embedded PE headers (MZ). The script extracts and categorizes printable strings.

Step 5: Decide and record

Classify as: dismiss, deep static, or detonate. Emit a triage record for the case file.

Validation

  • The detected type matches the file's structure (e.g. PE confirmed by MZ/PE\0\0).
  • Entropy reading is consistent with the strings observed (packed files yield few readable strings).
  • The triage record captures type, hashes, entropy, reputation, and the escalation decision.

Pitfalls

  • Equating "0 detections on VirusTotal" with benign — fresh or targeted malware is often unknown.
  • Treating high entropy alone as proof of malice; installers and compressed media are also high-entropy. Combine signals.
  • Uploading samples to third parties without authorization, leaking sensitive data.
  • Stopping at triage for a file that is clearly suspicious but "not yet detected."

References

  • See references/api-reference.md for the triage tool and scoring logic.
  • libmagic and VirusTotal API documentation (linked in frontmatter).

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosSíSí
Escribe archivosSíSí
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. MediaComando · command.base64_execscripts/analyst.py:33
  3. 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 2026da7600af1473edbFirmada–

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