triaging-an-unknown-sample
Performs fast first-pass triage of an unknown file to decide depth of analysis:
v1.0.03 instalações+3 em 7 dias24 EstrelasApache-2.0sincronizado há 10 horas
Instalar
Ainda não tem a CLI da NotHoly? Instale primeiro.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/triaging-an-unknown-sampleGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacotef1473edb…4aef2477
f1473edbe30d…94134aef24774 arquivos · 4.3 KBVarreduraMédio3 achados
- Script executável junto com a skillscripts/analyst.py
- command.base64_execscripts/analyst.py:33
- Links para domínios externos
Fontegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/triaging-an-unknown-sample@da7600a
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
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:
python scripts/analyst.py triage sample.bin
# reports: detected type, magic, hashes, entropy, suspicious stringsA .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:
python scripts/analyst.py reputation --sha256 <sha256> --vt-key $VT_API_KEYKnown-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:
entropy ~7.9 / 8.0 over most of the file -> likely packed/encrypted
mixed entropy with readable strings -> likely unpackedStep 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.mdfor the triage tool and scoring logic. - libmagic and VirusTotal API documentation (linked in frontmatter).
Arquivos desta versão
references/11.6 KB
- api-reference.md1.6 KB
scripts/13.8 KB
- analyst.py3.8 KB
- LICENSE340 B
- SKILL.md3.9 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Sim | Sim |
| Grava arquivos | Sim | Sim |
| Roda comandos no shell | Sim | Sim |
| Usa a rede | Sim | Sim |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
- MédiaArquivo · Script executável junto com a skillscripts/analyst.py
- MédiaComando · command.base64_execscripts/analyst.py:33
- InfoLink · Links para domínios externos
Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.
| Versão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v1.0.0 | 13 de nov. de 2026 | da7600a | f1473edb | Assinada | – |
Mais de meltedinhex
Tudo deste 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
Mais em Análise de malware e ransomware
Ver a 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
Pergunte tudo o que o seu escopo permite.
Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.
- 1/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login