handling-malware-samples-safely
Establishes safe practices for acquiring, storing, transferring, and disposing
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/handling-malware-samples-safelyEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquete4a7e415e…0c5f437b
4a7e415e95a3…14a80c5f437b4 archivos · 3.8 KBEscaneoMedio2 hallazgos
- Script ejecutable incluido con la skillscripts/analyst.py
- Enlaces a dominios externos
Fuentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/handling-malware-samples-safely@da7600a
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
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).
Archivos de esta versión
references/11.4 KB
- api-reference.md1.4 KB
scripts/12.8 KB
- analyst.py2.8 KB
- LICENSE340 B
- SKILL.md4.0 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | No | No |
| Ejecuta comandos de shell | Sí | Sí |
| Usa la red | Sí | Sí |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
- MediaArchivo · Script ejecutable incluido con la skillscripts/analyst.py
- InfoEnlace · Enlaces a dominios externos
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v1.0.0 | 13 nov 2026 | da7600a | 4a7e415e | Firmada | – |
Más de meltedinhex
Todo de este 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
Más en Análisis de malware y ransomware
Ver la categoría- 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
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/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login