handling-malware-samples-safely
Establishes safe practices for acquiring, storing, transferring, and disposing
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/handling-malware-samples-safelyScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto4a7e415e…0c5f437b
4a7e415e95a3…14a80c5f437b4 file · 3.8 KBScansioneMedio2 segnalazioni
- Script eseguibile incluso nella skillscripts/analyst.py
- Link a domini esterni
Sorgentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/handling-malware-samples-safely@da7600a
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
When to Use
- You are receiving, storing, or sharing a malicious file and need to prevent accidental execution or contamination.
- You need a consistent naming and identity scheme so a sample can be tracked across tools and tickets.
- You are packaging a sample to send to another analyst or a sandbox.
Do not use these conventions as a substitute for an isolated detonation environment; safe storage prevents accidents but analysis still requires an isolated lab.
Prerequisites
- An archive tool that supports password-protected, encrypted archives (7-Zip).
- A hashing utility (
sha256sum,certutil, or the bundled script). - A defined storage location with restricted access, separate from general file shares.
Safety & Handling
- Treat every sample as live. Never double-click; never leave it with its original executable extension on a working machine.
- Store samples inside an encrypted, password-protected archive with the conventional
password
infected. - Neutralize the extension on disk (e.g.
sample.exe→sample.exe.binorsample.exe_) so the OS will not execute it on a stray click. - Defang indicators in any text leaving the lab:
hxxp://,1.2.3[.]4,evil[.]com.
Workflow
Step 1: Identify the sample by hash
A sample's identity is its SHA-256, not its filename. Compute hashes immediately:
python scripts/analyst.py hash sample.exe
# md5, sha1, sha256, size, ssdeep-like size bucketRename the working copy to its SHA-256 so identity travels with the file:
mv sample.exe 9f86d0818...<sha256>.binStep 2: Store in an encrypted archive
7z a -p"infected" -mhe=on <sha256>.7z <sha256>.bin
# -mhe=on encrypts filenames tooKeep the loose, neutralized copy only inside the lab; the archive is the storage/transfer form.
Step 3: Record provenance
Capture where the sample came from, when, and who handled it. The script can emit a JSON metadata record:
python scripts/analyst.py record <sha256>.bin --source "MalwareBazaar" --case CASE-001Step 4: Defang before sharing
When pasting URLs/IPs into a report or ticket, defang them:
python scripts/analyst.py defang ioc.txt
# http://evil.com/x -> hxxp://evil[.]com/xValidation
7z l -slt <sha256>.7zshows encrypted headers (filenames not visible without password).- The on-disk working copy has a neutralized extension and matches the recorded SHA-256.
- The provenance record contains source, timestamp, case ID, and all three hashes.
- No raw clickable URLs/IPs remain in any artifact destined to leave the lab.
Pitfalls
- Sharing a sample in a plain zip — mail gateways and AV will quarantine or mangle it, and recipients risk accidental execution. Always password-encrypt.
- Trusting the filename or first-seen label as identity; only the hash is authoritative.
- Forgetting filename encryption (
-mhe=on), which leaks the sample name and your naming scheme. - Defanging only URLs but leaving live IPs or email addresses in the report.
References
- See
references/api-reference.mdfor the hashing, provenance, and defang tooling. - MalwareBazaar and NIST SP 800-86 (linked in frontmatter).
File di questa versione
references/11.4 KB
- api-reference.md1.4 KB
scripts/12.8 KB
- analyst.py2.8 KB
- LICENSE340 B
- SKILL.md4.0 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | Sì | Sì |
| Usa la rete | Sì | Sì |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- MediaFile · Script eseguibile incluso nella skillscripts/analyst.py
- InfoLink · Link a domini esterni
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v1.0.0 | 13 nov 2026 | da7600a | 4a7e415e | Firmata | – |
Altro da meltedinhex
Tutto da questo editore- 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
Altro in Analisi di malware e ransomware
Vai alla 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
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login