Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/triaging-an-unknown-sampleAnalisi di malware e ransomware

triaging-an-unknown-sample

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

v1.0.03 installazioni+3 in 7 giorni24 StelleApache-2.0sincronizzato 10 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/triaging-an-unknown-sample

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
YCBSDmdKgL…FGr8fqDQ==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchettof1473edb…4aef2477
f1473edbe30d…94134aef24774 file · ⁦4.3 KB⁩
ScansioneMedio3 segnalazioni
  • Script eseguibile incluso nella skillscripts/analyst.py
  • command.base64_execscripts/analyst.py:33
  • Link a domini esterni
Vedi la scansione completa
Sorgentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/triaging-an-unknown-sample@da7600a

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: 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).

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileSìSì
Scrive fileSìSì
Esegue comandi shellSìSì
Usa la reteSìSì
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

  1. MediaFile · Script eseguibile incluso nella skillscripts/analyst.py
  2. MediaComando · command.base64_execscripts/analyst.py:33
  3. InfoLink · Link a domini esterni

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v1.0.013 nov 2026da7600af1473edbFirmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login