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/performing-dynamic-analysis-in-a-sandboxAnálisis de malware y ransomware

performing-dynamic-analysis-in-a-sandbox

⁨Runs a sample in an instrumented sandbox to observe behavior: process tree, file⁩

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/performing-dynamic-analysis-in-a-sandbox

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

FirmaFirmado, ed25519
YOFbrm62he…fXQHAYDA==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquetea38a0d01…222813a0
a38a0d0104fb…9f26222813a04 archivos · ⁦3.3 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/performing-dynamic-analysis-in-a-sandbox@da7600a

Esta entrada todavía no está escrita en tu idioma, así que aparece en English.

When to Use

  • Static analysis is blocked by packing/obfuscation and you need to observe runtime behavior.
  • You want a behavioral picture: spawned processes, dropped files, registry edits, and C2.
  • You are confirming capabilities hypothesized from static analysis.

Do not use dynamic analysis as the only method — evasive samples may sleep, detect the sandbox, or require arguments. Pair it with static/RE work.

Prerequisites

  • An isolated lab with a victim VM and simulated internet (see the lab-setup skill).
  • A sandbox stack (CAPE/Cuckoo) or manual instrumentation: Process Monitor, Process Explorer, Regshot, and a packet capture on the services guest.
  • A clean base snapshot to revert to.

Safety & Handling

  • Detonate only inside the isolated victim VM; revert the snapshot after each run.
  • Route all network through the simulated-internet guest; never allow live egress.
  • Defang any captured URLs/IPs before they leave the lab.

Workflow

Step 1: Prepare instrumentation

Start Process Monitor (filtered to the target), Regshot baseline, and packet capture on the services guest. Snapshot the victim as clean.

Step 2: Detonate with the right context

Many samples need a parent (Office, rundll32), an export (rundll32 dll,Export), or arguments. Match the original delivery context or the sample stalls.

Step 3: Observe for the full behavior window

Watch process creation, file drops, registry Run keys/services, scheduled tasks, and network beacons. Give it several minutes; some samples sleep first.

Step 4: Summarize the report

Feed the sandbox JSON (or your collected logs) to the summarizer to group events into capabilities and IOCs:

bash
python scripts/analyst.py summarize report.json

Step 5: Diff the system state

Compare Regshot/file baselines pre- and post-run to capture persistence and dropped artifacts.

Validation

  • The observed process tree and network match the static-analysis hypothesis.
  • Persistence mechanisms found dynamically are confirmed in registry/task artifacts.
  • Re-running from the clean snapshot reproduces the core behavior.

Pitfalls

  • Detonating without the required parent/args, so the sample exits early ("sandbox evasion" that is really a context problem).
  • Too-short observation windows that miss sleeping or staged payloads.
  • Trusting a single sandbox verdict; tune and corroborate.
  • Allowing real network egress and contaminating live infrastructure.

References

  • See references/api-reference.md for the report summarizer.
  • CAPE Sandbox and Process Monitor (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 2026da7600aa38a0d01Firmada–

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