Skip to content
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-volatility3Malware and ransomware analysis

analyzing-malware-in-memory-with-volatility3

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

v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/analyzing-malware-in-memory-with-volatility3

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
ijy9Ilt+lH…tvpLjcCQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package12fd2a56…f83f2ddd
12fd2a56d3a8…c877f83f2ddd4 files · ⁦3.3 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/analyst.py
  • Links to outside domains
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/analyzing-malware-in-memory-with-volatility3@da7600a

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).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesYesYes
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/analyst.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600a12fd2a56Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login