Skip to main content ホーム クリエイター yaklang hack-skills memory-forensics-volatility
memory-forensics-volatility Memory forensics playbook using Volatility 2/3. Use when analyzing memory dumps for malware analysis, credential extraction, process investigation, code injection detection, and incident response timeline reconstruction.
インストールへ移動 Skills Marketplace コミュニティが作成したAIスキルを発見・探索
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/yaklang/hack-skills --skill memory-forensics-volatilityコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか?SkillsMP が現在取得できるファイルをダウンロードできます。
Zipをダウンロード ダウンロード中... VOLATILITY_CHEATSHEET.md 6.3 KB name memory-forensics-volatility description Memory forensics playbook using Volatility 2/3. Use when analyzing memory dumps for malware analysis, credential extraction, process investigation, code injection detection, and incident response timeline reconstruction.
SKILL: Memory Forensics — Expert Analysis Playbook
AI LOAD INSTRUCTION : Expert memory forensics techniques using Volatility 2 and 3. Covers memory acquisition, OS identification, process analysis (hidden process detection), network connections, DLL/module analysis, code injection detection (malfind), credential extraction, file carving, registry analysis, and timeline generation. Base models miss the Vol2/Vol3 command differences, malware indicator patterns, and Linux-specific memory analysis.
0. RELATED ROUTING
Before going deep, consider loading:
Quick Reference
Also load VOLATILITY_CHEATSHEET.md when you need:
Vol2 vs Vol3 command comparison table
Common plugin sequences for specific investigation types
1. MEMORY ACQUISITION
Linux
insmod lime.ko "path=/tmp/mem.lime format=lime"
dd if =/proc/kcore of=/tmp/mem.raw bs=1M
./avml /tmp/mem.lime
Windows
winpmem_mini_x64.exe memdump.raw
DumpIt.exe
MagnetRAMCapture.exe /output memdump.raw
Virtual Machines
2. VOLATILITY 2 vs 3 Concept Volatility 2 Volatility 3 Profile system --profile=Win10x64_19041Auto-detected (symbol tables) Image info imageinfowindows.info / linux.infoProcess list pslistwindows.pslistNetwork netscan / connectionswindows.netscan / windows.netstatDLLs dlllistwindows.dlllistInjection malfindwindows.malfindHashes hashdumpwindows.hashdumpFiles filescanwindows.filescanRegistry hivelist / printkeywindows.registry.hivelist / windows.registry.printkeyInstall pip2 install volatilitypip3 install volatility3
3. ANALYSIS METHODOLOGY
Step 1: Identify OS
vol.py -f mem.raw imageinfo
vol.py -f mem.raw kdbgscan
vol -f mem.raw windows.info
vol -f mem.raw banners.Banners
Step 2: Process Listing — Hidden Process Detection
vol.py -f mem.raw --profile=PROFILE pslist
vol.py -f mem.raw --profile=PROFILE psscan
vol.py -f mem.raw --profile=PROFILE pstree
vol -f mem.raw windows.pslist
vol -f mem.raw windows.psscan
vol -f mem.raw windows.pstree
Red flags : Process in psscan but not pslist = DKOM (Direct Kernel Object Manipulation) hiding.
Step 3: Network Connections
vol.py -f mem.raw --profile=PROFILE netscan
vol.py -f mem.raw --profile=PROFILE connections
vol.py -f mem.raw --profile=PROFILE connscan
vol -f mem.raw windows.netscan
vol -f mem.raw windows.netstat
Step 4: DLL / Module Analysis
vol.py -f mem.raw --profile=PROFILE dlllist -p PID
vol.py -f mem.raw --profile=PROFILE ldrmodules -p PID
vol -f mem.raw windows.dlllist --pid PID
Red flags : DLL in dlllist but False in all three ldrmodules columns = reflective DLL injection.
Step 5: Code Injection Detection (Malfind)
vol.py -f mem.raw --profile=PROFILE malfind -p PID
vol.py -f mem.raw --profile=PROFILE malfind -D /tmp/dump/
vol -f mem.raw windows.malfind --pid PID
What malfind detects : Memory regions with PAGE_EXECUTE_READWRITE that don't map to a file on disk — classic shellcode/injection indicator.
Step 6: Credential Extraction
vol.py -f mem.raw --profile=PROFILE hashdump
vol.py -f mem.raw --profile=PROFILE lsadump
vol.py -f mem.raw --profile=PROFILE cachedump
vol.py -f mem.raw --profile=PROFILE mimikatz
vol -f mem.raw windows.hashdump
vol -f mem.raw windows.lsadump
vol -f mem.raw windows.cachedump
Step 7: File Extraction
vol.py -f mem.raw --profile=PROFILE filescan | grep -i "password\|secret\|flag"
vol.py -f mem.raw --profile=PROFILE dumpfiles -Q OFFSET -D /tmp/dump/
vol -f mem.raw windows.filescan
vol -f mem.raw windows.dumpfiles --virtaddr OFFSET
Step 8: Registry Analysis
vol.py -f mem.raw --profile=PROFILE hivelist
vol.py -f mem.raw --profile=PROFILE printkey -K "Software\Microsoft\Windows\CurrentVersion\Run"
vol.py -f mem.raw --profile=PROFILE userassist
vol -f mem.raw windows.registry.hivelist
vol -f mem.raw windows.registry.printkey --key "Software\Microsoft\Windows\CurrentVersion\Run"
Step 9: Command History
vol.py -f mem.raw --profile=PROFILE cmdscan
vol.py -f mem.raw --profile=PROFILE consoles
vol -f mem.raw windows.cmdline
Step 10: Timeline Generation
vol.py -f mem.raw --profile=PROFILE timeliner --output=body --output-file=timeline.body
mactime -b timeline.body -d > timeline.csv
vol -f mem.raw timeliner.Timeliner
4. LINUX MEMORY ANALYSIS
vol.py -f mem.lime --profile=LinuxProfile linux_pslist
vol.py -f mem.lime --profile=LinuxProfile linux_pstree
vol.py -f mem.lime --profile=LinuxProfile linux_netstat
vol.py -f mem.lime --profile=LinuxProfile linux_bash
vol.py -f mem.lime --profile=LinuxProfile linux_enumerate_files
vol.py -f mem.lime --profile=LinuxProfile linux_proc_maps -p PID
vol.py -f mem.lime --profile=LinuxProfile linux_malfind
vol -f mem.lime linux.pslist
vol -f mem.lime linux.pstree
vol -f mem.lime linux.bash
vol -f mem.lime linux.check_afinfo
vol -f mem.lime linux.check_syscall
vol -f mem.lime linux.tty_check
Building Linux Profiles (Vol2) cd volatility/tools/linux
make
zip LinuxProfile.zip module.dwarf /boot/System.map-$(uname -r)
5. MALWARE INDICATORS IN MEMORY Indicator Detection Method What It Means Process in psscan but not pslist Compare pslist vs psscan DKOM — process hiding Unexpected parent-child pstree analysis e.g., svchost spawned by cmd.exe MZ header in non-image memory malfind Reflective DLL / PE injection RWX memory without backing file malfind Shellcode injection DLL unlinked from all PEB lists ldrmodules (all False) Stealth DLL loading svchost.exe not child of services.exe pstree Fake svchost (malware) Unusual network connections netscan + PID correlation C2 communication Hooking in SSDT/IDT ssdt / idt plugins Rootkit Modified kernel objects linux_check_syscall Linux rootkit
Normal Parent-Child Relationships (Windows) System (4)
└── smss.exe
└── csrss.exe
└── wininit.exe
└── services.exe
└── svchost.exe (multiple)
└── spoolsv.exe
└── lsass.exe
└── winlogon.exe
└── explorer.exe
└── user applications
6. DECISION TREE Memory dump acquired — need to analyze
│
├── What OS?
│ ├── Windows → vol imageinfo / windows.info (§3 Step 1)
│ └── Linux → build profile or use Vol3 auto-detect (§4)
│
├── Malware investigation?
│ ├── Check processes: pslist vs psscan (hidden?) (§3 Step 2)
│ ├── Check parent-child: pstree (suspicious spawning?) (§5)
│ ├── Check injections: malfind (RWX memory?) (§3 Step 5)
│ ├── Check DLLs: ldrmodules (unlinked?) (§3 Step 4)
│ ├── Check network: netscan (C2 connections?) (§3 Step 3)
│ └── Extract suspicious files: dumpfiles (§3 Step 7)
│
├── Credential recovery?
│ ├── SAM hashes → hashdump (§3 Step 6)
│ ├── LSA secrets → lsadump (§3 Step 6)
│ ├── Cached domain creds → cachedump (§3 Step 6)
│ └── Plaintext passwords → mimikatz plugin (§3 Step 6)
│
├── Incident timeline?
│ ├── timeliner for comprehensive timeline (§3 Step 10)
│ ├── cmdscan / consoles for command history (§3 Step 9)
│ ├── userassist for program execution (§3 Step 8)
│ └── Cross-reference with PCAP timeline (→ traffic-analysis-pcap)
│
├── CTF / flag hunting?
│ ├── filescan + grep for flag patterns (§3 Step 7)
│ ├── cmdscan for typed flags/passwords (§3 Step 9)
│ ├── Clipboard: clipboard plugin
│ ├── Screenshots: screenshot plugin
│ └── Environment vars: envars plugin
│
└── Linux-specific?
├── linux_bash for shell history (§4)
├── linux_check_syscall for rootkit (§4)
└── linux_netstat for connections (§4)