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-volatility3Writes to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package12fd2a56…f83f2ddd
12fd2a56d3a8…c877f83f2ddd4 files · 3.3 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/analyzing-malware-in-memory-with-volatility3@da7600a
On this page
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
vol -f memory.raw windows.pslist
vol -f memory.raw windows.pstreeLook for unusual parents (Word spawning cmd/powershell), masquerading names
(scvhost.exe), processes with no disk path, and orphaned children.
Step 2: Hunt injected code
vol -f memory.raw windows.malfindmalfind flags private, executable, RWX regions with no backing file — classic injection.
Note the PID and base address for dumping.
Step 3: Review network connections
vol -f memory.raw windows.netscanCorrelate 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:
vol -f memory.raw windows.dumpfiles --pid <pid>The helper script parses Volatility's JSON renderer output to highlight injection candidates.
vol -f memory.raw -r json windows.malfind | python scripts/analyst.py malfind -Validation
- Injection candidates from
malfindcorrespond to anomalous processes frompstree. - 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.mdfor the malfind output parser. - Volatility 3 documentation and memory-forensics concepts (linked in frontmatter).
Files in this version
references/11.2 KB
- api-reference.md1.2 KB
scripts/12.3 KB
- analyst.py2.3 KB
- LICENSE340 B
- SKILL.md3.6 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | Yes | Yes |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumFile · Executable script shipped with the skillscripts/analyst.py
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v1.0.0 | Nov 13, 2026 | da7600a | 12fd2a56 | Signed | – |
More from meltedinhex
All from this publisher- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
More in Malware and ransomware analysis
See the category- yara-sigsdariushoule/yara-sigs4
- monitoring-darkweb-sourcesmukul975/monitoring-darkweb-sources3
- deploying-ransomware-canary-filesmukul975/deploying-ransomware-canary-files3
- implementing-honeypot-for-ransomware-detectionmukul975/implementing-honeypot-for-ransomware-detection3
- yaraaeondave/yara3
- testing-ransomware-recovery-proceduresmukul975/testing-ransomware-recovery-procedures3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login