Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
meltedinhex/triaging-an-unknown-sampleAnálise de malware e ransomware

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

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
YCBSDmdKgL…FGr8fqDQ==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacotef1473edb…4aef2477
f1473edbe30d…94134aef24774 arquivos · ⁦4.3 KB⁩
VarreduraMédio3 achados
  • Script executável junto com a skillscripts/analyst.py
  • command.base64_execscripts/analyst.py:33
  • Links para domínios externos
Ver a varredura completa
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.

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).

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosSimSim
Grava arquivosSimSim
Roda comandos no shellSimSim
Usa a redeSimSim
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

  1. MédiaArquivo · Script executável junto com a skillscripts/analyst.py
  2. MédiaComando · command.base64_execscripts/analyst.py:33
  3. 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ãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v1.0.013 de nov. de 2026da7600af1473edbAssinada–

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

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login