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/performing-dynamic-analysis-in-a-sandboxAnalisi di malware e ransomware

performing-dynamic-analysis-in-a-sandbox

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

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

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

FirmaFirmato, ed25519
YOFbrm62he…fXQHAYDA==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchettoa38a0d01…222813a0
a38a0d0104fb…9f26222813a04 file · ⁦3.3 KB⁩
ScansioneMedio2 segnalazioni
  • Script eseguibile incluso nella skillscripts/analyst.py
  • Link a domini esterni
Vedi la scansione completa
Sorgentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/performing-dynamic-analysis-in-a-sandbox@da7600a

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

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
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. 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 2026da7600aa38a0d01Firmata–

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