meltedinhex/analyst-ai-pack / skills/analyzing-malware-in-memory-with-volatility3
analyzing-malware-in-memory-with-volatility3
VerifiedAnalyzes a memory image with Volatility 3 to find malware: rogue processes, injected code, suspicious network connections, loaded modules, and persistence, then extracts artifacts for further analysis. Activates for requests to do memory forensics, analyze a RAM dump, or hunt malware in memory with Volatility.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 340 B |
| SKILL.md | skill md | 3.6 KB |
| references/api-reference.md | markdown | 1.2 KB |
| scripts/analyst.py | script | 2.3 KB |
references/api-reference.md
View on GitHub# API Reference: Analyzing Malware in Memory with Volatility 3
## Overview
`scripts/analyst.py` consumes Volatility 3 `windows.malfind` JSON output and ranks memory
regions by injection signal (RWX protection, embedded MZ header, executable prologue). It
analyzes plugin output, not raw memory.
## Dependencies
| Package | Version | Purpose |
|---------|---------|---------|
| (stdlib) | — | JSON parsing |
| volatility3 | >= 2.5 | Produces the memory-plugin output this tool consumes |
## External tools
| Tool | Purpose |
|------|---------|
| Volatility 3 | Memory image analysis (pslist, pstree, malfind, netscan, dumpfiles) |
| WinPmem / LiME | Memory acquisition |
## Core functions
### `rank_malfind(doc)`
Parses malfind rows and scores each by injection indicators, returning a sorted candidate
list with PID, process, address, and protection.
## Usage
```bash
pip install volatility3
vol -f memory.raw -r json windows.malfind | python scripts/analyst.py malfind -
```
## Sources
- Volatility 3 documentation — https://volatility3.readthedocs.io/
- The Art of Memory Forensics — concepts of injection detection (malfind/RWX)
- Volatility 3 JSON renderer output structure (project docs)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |