Individual skill
analyzing-memory-images
Analyze volatile memory images (RAM dumps) using Volatility 3 — process enumeration, injected code detection, credential extraction, network artifacts, rootkit analysis, and timeline construction from memory-resident data. Use when examining a memory capture from a compromised host, hunting for injected code or hollowed processes, extracting credentials or network state from RAM, or detecting kernel-level rootkits.
secskills-defense/skills/analyzing-memory-images/SKILL.md
Source commit ca53957bcd8e3b83b5d4d190bb3ad008a4f15c84
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 188
- Repository last updated
- Sep 4, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- security Repository topic
- skills Repository topic
- operations Derived category
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 16,151 bytesSKILL.mdcore · 16,151 bytesSKILL.mdcore · 16,151 bytesSKILL.mdcore · 16,151 bytesSKILL.mdcore · 16,151 bytesSKILL.mdcore · 16,151 bytesSKILL.mdcore · 16,151 bytesSKILL.mdcore · 16,151 bytesSKILL.mdcore · 16,151 bytesSKILL.mdcore · 16,151 bytesSKILL.mdcore · 16,151 bytesSKILL.mdcore · 16,151 bytesSKILL.mdcore · 16,151 bytesSKILL.mdcore · 16,151 bytesSKILL.mdcore · 16,151 bytesSKILL.mdcore · 16,151 bytesSKILL.mdcore · 16,151 bytes
Read excerpt
# Analyzing Memory Images
Memory is the only place certain artifacts exist — injected code, decrypted
payloads, credential material, and network connections from processes that have
already exited. Disk forensics misses all of these. The work is getting the
image before it is lost, then asking the right questions in the right order.
## When to Use
- You have a memory dump (raw, LiME, EWF, crash dump, or VM snapshot) to analyze
- Investigating a compromised host and need artifacts that exist only in RAM
- Looking for injected code, process hollowing, or reflective DLL loading
- Extracting credential material — hashes, Kerberos tickets, cached credentials
- Identifying network connections and listening ports from a point-in-time capture