Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
meltedinhex/handling-malware-samples-safelyAnálisis de malware y ransomware

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

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
Fgjozegxxx…GQW3PPDg==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete4a7e415e…0c5f437b
4a7e415e95a3…14a80c5f437b4 archivos · ⁦3.8 KB⁩
EscaneoMedio2 hallazgos
  • Script ejecutable incluido con la skillscripts/analyst.py
  • Enlaces a dominios externos
Ver el escaneo completo
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.

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.bin or sample.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:

bash
python scripts/analyst.py hash sample.exe
# md5, sha1, sha256, size, ssdeep-like size bucket

Rename the working copy to its SHA-256 so identity travels with the file:

bash
mv sample.exe 9f86d0818...<sha256>.bin

Step 2: Store in an encrypted archive

bash
7z a -p"infected" -mhe=on <sha256>.7z <sha256>.bin
# -mhe=on encrypts filenames too

Keep 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:

bash
python scripts/analyst.py record <sha256>.bin --source "MalwareBazaar" --case CASE-001

Step 4: Defang before sharing

When pasting URLs/IPs into a report or ticket, defang them:

bash
python scripts/analyst.py defang ioc.txt
# http://evil.com/x -> hxxp://evil[.]com/x

Validation

  • 7z l -slt <sha256>.7z shows 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.md for the hashing, provenance, and defang tooling.
  • MalwareBazaar and NIST SP 800-86 (linked in frontmatter).

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellSíSí
Usa la redSíSí
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

  1. MediaArchivo · Script ejecutable incluido con la skillscripts/analyst.py
  2. InfoEnlace · Enlaces a dominios externos

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v1.0.013 nov 2026da7600a4a7e415eFirmada–

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

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login