Skip to content
Skills Library
Security · Analysis

memory-forensics

/memory-forensics

Analyze Windows and Linux memory images with Volatility 3 to find malicious processes, injected code, network connections, command lines, persistence and credential-theft artefacts. Use when a memory dump (.raw, .lime, .vmem, hiberfil, crash dump) is available or when fileless malware or process injection is suspected.

Repository
Claude-Blue ↗
Licence
MIT
Last repository change
01.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
4
Deprecation

No signals detected. Repository changed on 01.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Analyze Windows and Linux memory images with Volatility 3 to find malicious processes, injected code, network connections, command lines, persistence and credential-theft artefacts. Use when a memory dump (.raw, .lime, .vmem, hiberfil, crash dump) is available or when fileless malware or process injection is suspected.

Original author description

Analyze Windows and Linux memory images with Volatility 3 to find malicious processes, injected code, network connections, command lines, persistence and credential-theft artefacts. Use when a memory dump (.raw, .lime, .vmem, hiberfil, crash dump) is available or when fileless malware or process injection is suspected.

How it works

  1. Setup
  2. Triage sequence (Windows)
  3. Linux
  4. Interpretation
  5. Output template
  6. Safety
  7. Related skills
  8. References
Original SKILL.md headings · 64 lines, 402 words
SKILL.md preview
---
name: memory-forensics
description: Analyze Windows and Linux memory images with Volatility 3 to find malicious processes, injected code, network connections, command lines, persistence and credential-theft artefacts. Use when a memory dump (.raw, .lime, .vmem, hiberfil, crash dump) is available or when fileless malware or process injection is suspected.
license: MIT
metadata:
  category: dfir
  version: "2.0.0"
  verification: documented
---

# Memory Forensics (Volatility 3)

## Setup

```sh
pip install volatility3          # or clone https://github.com/volatilityfoundation/volatility3
vol -f mem.raw windows.info      # confirms symbols/profile load; Linux needs matching ISF symbols
```
Linux images need an ISF symbol file for the exact kernel (`dwarf2json` from vmlinux with debug symbols).

## Triage sequence (Windows)

| Step | Plugin | Look for |
|---|---|---|
| Processes | `windows.pslist`, `windows.psscan`, `windows.pstree` | Hidden processes (in psscan not pslist), wrong parents (e.g. `lsass.exe` not child of `wininit.exe`; `svchost.exe` not child of `services.exe`), misspelled names, odd paths |
| Command lines | `windows.cmdline` | Encoded PowerShell, LOLBins, paths in `%TEMP%`/`AppData` |
| Network | `windows.netscan` | Connections from processes that shouldn't talk (e.g. `notepad.exe`), listeners on unusual ports |
| Injection | `windows.malfind` | `PAGE_EXECUTE_READWRITE` private regions with MZ header or shellcode |
| Modules | `windows.dlllist`, `windows.ldrmodules` | DLLs from user-writable paths; unlinked modules (InLoad/InInit/InMem = False) |
| Services | `windows.svcscan` | Services with binaries in unusual paths or recently added |
| Handles/mutex | `windows.handles --pid N` | Known malware mutexes, handles to `lsass.exe` |
| Registry | `windows.registry.hivelist`, `windows.registry.printkey --key "Software\Microsoft\Windows\CurrentVersion\Run"` | Persistence |
| Files | `windows.filescan`, `windows.dumpfiles --virtaddr 0x...` | Recover binaries/scripts for analysis |
| Process dump | `windows.pslist --pid N --dump`, `windows.memmap --pid N --dump` | Feed to YARA/static analysis |

YARA over memory: `vol -f mem.raw windows.vadyarascan --yara-file rules.yar` (plugin name/options vary by version — check `vol -h`).

## Linux

`linux.pslist`, `linux.pstree`, `linux.bash` (shell history from memory), `linux.lsof`, `linux.sockstat`, `linux.malfind`, `linux.check_modules` / `linux.lsmod` (hidden kernel modules), `linux.elfs`.

## Interpretation

- Baseline parent/child relationships: SANS "Hunt Evil" poster is a practical reference.
- Malfind has false positives (JIT engines: .NET, browsers, Java). Confirm with a dump + YARA/disassembly.
- Correlate memory findings with disk timeline and EDR telemetry; record PID, process create time and virtual addresses.

## Output template

```
Image: <file> sha256 <>  OS: <build>  Captured: <UTC>
Suspicious processes: <pid> <name> <ppid> <path> <reason>
Injection: <pid> <vad addr> <protection> <evidence>
Network: <pid> <local> → <remote> <state>
Persistence: <>
Extracted artefacts: <file> sha256 <>
Confidence & next steps: <>
```

## Safety

Analyse on an isolated analysis workstation. Dumped executables are live malware — store in password-protected archives (`infected`) and never execute outside a sandbox.

## Related skills

`forensic-imaging`, `windows-artifacts`, `yara-authoring`, `credential-theft-detection`, `pe-static-analysis`

## References

- Volatility 3 docs: https://volatility3.readthedocs.io/
- Volatility 3 repository: https://github.com/volatilityfoundation/volatility3
- SANS DFIR "Hunt Evil" poster: https://www.sans.org/posters/hunt-evil/

Versions

RepositoryScoreLicence
This page · kaandgnsh/Claude-Blue100MIT
rootcastleco/rei-skills100MIT
rmyndharis/antigravity-skills100MIT
wshobson/agents100MIT

Database snapshot: 13.11.2026 · package version 158d3a8389c0 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100analyzing-memory-forensics-with-lime-and-volatility
    Performs Linux memory acquisition using LiME (Linux Memory Extractor) kernel module and analysis with Volatility 3 framework. Extracts process lists, network connections, bash history, loaded kernel modules, and injected code from Linux memory images. Use when performing…
  • 100memory-forensics-dump-acquisition-analysis
    Use this skill when acquire bit-stream RAM captures safely from live Windows and Linux systems for offline triage.
  • 100memory-forensics-volatility3-process-tree
    Use this skill when inspect volatile memory dumps, hidden processes, and DLL injections using Volatility 3.
  • 90memory-forensics-triage
    Triages supplied Windows, Linux, or other volatile-memory images while preserving acquisition provenance, image integrity, process and region evidence, network and object correlations, extracted-artifact custody, timeline limits, and claim confidence. Use for offline…
  • 98detecting-fileless-malware-techniques
    Detects and analyzes fileless malware that operates entirely in memory using PowerShell, WMI, .NET reflection, registry-resident payloads, and living-off-the-land binaries (LOLBins) without writing traditional executable files to disk. Use for requests involving fileless threat…
  • 100disk-forensics
    Analyze disk images, file systems, and memory captures for digital evidence recovery in forensic investigations and CTF challenges. Use when the user mentions 'disk forensics,' 'forensic analysis,' 'disk image,' 'file carving,' 'deleted files,' 'evidence recovery,' 'timeline…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.