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/analyzing-malware-in-memory-with-volatility3Analisi di malware e ransomware

analyzing-malware-in-memory-with-volatility3

⁨Analyzes a memory image with Volatility 3 to find malware: rogue processes,⁩

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/analyzing-malware-in-memory-with-volatility3

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

FirmaFirmato, ed25519
ijy9Ilt+lH…tvpLjcCQ==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto12fd2a56…f83f2ddd
12fd2a56d3a8…c877f83f2ddd4 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/analyzing-malware-in-memory-with-volatility3@da7600a

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

When to Use

  • You have a RAM image from a suspected-infected host and need to find malicious activity.
  • Disk artifacts are insufficient (fileless/in-memory malware) and you need volatile evidence.
  • You want to extract injected code, command lines, or network connections for analysis.

Do not use Volatility plugins blindly without an order of investigation — start broad (processes, network) before deep per-process dumps.

Prerequisites

  • Volatility 3 (pip install volatility3) with appropriate symbol tables.
  • A memory image acquired with a sound tool (WinPmem, LiME, or hypervisor snapshot).
  • Knowledge of the source OS/version to select the right symbols.

Safety & Handling

  • Work on a copy of the image; preserve the original with a recorded hash.
  • Treat any dumped executable region as a live sample — store and handle it accordingly.

Workflow

Step 1: Enumerate processes and spot anomalies

bash
vol -f memory.raw windows.pslist
vol -f memory.raw windows.pstree

Look for unusual parents (Word spawning cmd/powershell), masquerading names (scvhost.exe), processes with no disk path, and orphaned children.

Step 2: Hunt injected code

bash
vol -f memory.raw windows.malfind

malfind flags private, executable, RWX regions with no backing file — classic injection. Note the PID and base address for dumping.

Step 3: Review network connections

bash
vol -f memory.raw windows.netscan

Correlate listening/established connections with suspicious PIDs and the C2 endpoints from other analysis.

Step 4: Check modules, handles, and persistence

Examine loaded DLLs (windows.dlllist), services, and registry (windows.registry.*) for persistence and unexpected modules.

Step 5: Dump artifacts

Dump the suspicious process or injected region for static/RE analysis:

bash
vol -f memory.raw windows.dumpfiles --pid <pid>

The helper script parses Volatility's JSON renderer output to highlight injection candidates.

bash
vol -f memory.raw -r json windows.malfind | python scripts/analyst.py malfind -

Validation

  • Injection candidates from malfind correspond to anomalous processes from pstree.
  • Network connections map to known C2 or the sample's extracted config.
  • Dumped regions disassemble into meaningful code, not random bytes.

Pitfalls

  • Wrong symbols/profile producing empty or garbage results — confirm OS build first.
  • Treating every RWX region as malicious; some legitimate JIT engines use RWX. Corroborate.
  • Forgetting to hash and preserve the original image before analysis.

References

  • See references/api-reference.md for the malfind output parser.
  • Volatility 3 documentation and memory-forensics concepts (linked in frontmatter).

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileSìSì
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 2026da7600a12fd2a56Firmata–

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