Skip to main content
memory-forensics Master memory forensics techniques including memory acquisition, process analysis, and artifact extraction using Volatility and related tools. Use when analyzing memory dumps, investigating incidents, or performing malware analysis from RAM captures.
Ir para a instalação Skills Marketplace Descubra e explore skills de IA criadas pela comunidade.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Copiar promptMostrar detalhes do prompt Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
npx skills add https://github.com/oimiragieo/agent-studio --skill memory-forensicsO comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.
Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.
Baixar Zip Baixando... Explorador de arquivos
10 arquivos Ocupações relacionadas SOC
Baseado na classificação ocupacional SOC
name memory-forensics description Master memory forensics techniques including memory acquisition, process analysis, and artifact extraction using Volatility and related tools. Use when analyzing memory dumps, investigating incidents, or performing malware analysis from RAM captures. version 1.1.0 model sonnet invoked_by ["reverse-engineer","security-architect","incident-responder"] tools ["Read","Write","Edit","Bash","Glob","Grep"] verified true lastVerifiedAt "2026-02-22T00:00:00.000Z" source builtin trust_score 100 provenance_sha 7f3ede585d3c577a
Memory Forensics
Security Notice
AUTHORIZED USE ONLY : These skills are for DEFENSIVE security analysis and authorized research:
Incident response with proper authorization
Forensic investigations in authorized contexts
Malware analysis for defensive purposes
CTF competitions and security research
Educational purposes in controlled environments
NEVER use for :
Unauthorized system access or surveillance
Privacy violations
Intellectual property theft
Any illegal activities
Comprehensive techniques for acquiring, analyzing, and extracting artifacts from memory dumps for incident response and malware analysis.
Memory Acquisition
Live Acquisition Tools
Windows
# WinPmem (Recommended)
winpmem_mini_x64.exe memory.raw
# DumpIt
DumpIt.exe
# Belkasoft RAM Capturer
# GUI-based, outputs raw format
# Magnet RAM Capture
# GUI-based, outputs raw format
Linux
sudo insmod lime.ko "path=/tmp/memory.lime format=lime"
sudo dd if =/dev/mem of=memory.raw bs=1M
sudo cp /proc/kcore memory.elf
macOS
sudo ./osxpmem -o memory.raw
Virtual Machine Memory
cp vm.vmem memory.raw
vboxmanage debugvm "VMName" dumpvmcore --filename memory.elf
virsh dump <domain> memory.raw --memory-only
Volatility 3 Framework
Installation and Setup
pip install volatility3
vol -f memory.raw <plugin>
vol -f memory.raw -s /path/to/symbols windows.pslist
Essential Plugins
Process Analysis
vol -f memory.raw windows.pslist
vol -f memory.raw windows.pstree
vol -f memory.raw windows.psscan
vol -f memory.raw windows.memmap --pid <PID> --dump
vol -f memory.raw windows.envars --pid <PID>
vol -f memory.raw windows.cmdline
Network Analysis
vol -f memory.raw windows.netscan
vol -f memory.raw windows.netstat
DLL and Module Analysis
vol -f memory.raw windows.dlllist --pid <PID>
vol -f memory.raw windows.ldrmodules
vol -f memory.raw windows.modules
vol -f memory.raw windows.moddump --pid <PID>
Memory Injection Detection
vol -f memory.raw windows.malfind
vol -f memory.raw windows.vadinfo --pid <PID>
vol -f memory.raw windows.vadyarascan --yara-rules rules.yar
Registry Analysis
vol -f memory.raw windows.registry.hivelist
vol -f memory.raw windows.registry.printkey --key "Software\Microsoft\Windows\CurrentVersion\Run"
vol -f memory.raw windows.registry.hivescan --dump
File System Artifacts
vol -f memory.raw windows.filescan
vol -f memory.raw windows.dumpfiles --pid <PID>
vol -f memory.raw windows.mftscan
Linux Analysis
vol -f memory.raw linux.pslist
vol -f memory.raw linux.pstree
vol -f memory.raw linux.bash
vol -f memory.raw linux.sockstat
vol -f memory.raw linux.lsmod
vol -f memory.raw linux.mount
vol -f memory.raw linux.envars
macOS Analysis
vol -f memory.raw mac.pslist
vol -f memory.raw mac.pstree
vol -f memory.raw mac.netstat
vol -f memory.raw mac.lsmod
Analysis Workflows
Malware Analysis Workflow
vol -f memory.raw windows.pstree > processes.txt
vol -f memory.raw windows.pslist > pslist.txt
vol -f memory.raw windows.netscan > network.txt
vol -f memory.raw windows.malfind > malfind.txt
vol -f memory.raw windows.dlllist --pid <PID>
vol -f memory.raw windows.handles --pid <PID>
vol -f memory.raw windows.pslist --pid <PID> --dump
strings -a pid.<PID>.exe > strings.txt
vol -f memory.raw windows.yarascan --yara-rules malware.yar
Incident Response Workflow
vol -f memory.raw windows.timeliner > timeline.csv
vol -f memory.raw windows.cmdline
vol -f memory.raw windows.consoles
vol -f memory.raw windows.registry.printkey \
--key "Software\Microsoft\Windows\CurrentVersion\Run"
vol -f memory.raw windows.svcscan
vol -f memory.raw windows.scheduled_tasks
vol -f memory.raw windows.filescan | grep -i "recent"
Data Structures
Windows Process Structures
typedef struct _EPROCESS {
KPROCESS Pcb;
EX_PUSH_LOCK ProcessLock;
LARGE_INTEGER CreateTime;
LARGE_INTEGER ExitTime;
LIST_ENTRY ActiveProcessLinks;
ULONG_PTR UniqueProcessId;
PEB* Peb;
} EPROCESS;
typedef struct _PEB {
BOOLEAN InheritedAddressSpace;
BOOLEAN ReadImageFileExecOptions;
BOOLEAN BeingDebugged;
PVOID ImageBaseAddress;
PPEB_LDR_DATA Ldr;
PRTL_USER_PROCESS_PARAMETERS ProcessParameters;
} PEB;
VAD (Virtual Address Descriptor) typedef struct _MMVAD {
MMVAD_SHORT Core;
union {
ULONG LongFlags;
MMVAD_FLAGS VadFlags;
} u;
PVOID FirstPrototypePte;
PVOID LastContiguousPte;
PFILE_OBJECT FileObject;
} MMVAD;
#define PAGE_EXECUTE 0x10
#define PAGE_EXECUTE_READ 0x20
#define PAGE_EXECUTE_READWRITE 0x40
#define PAGE_EXECUTE_WRITECOPY 0x80
Detection Patterns
Process Injection Indicators
Rootkit Detection
vol -f memory.raw windows.pslist > pslist.txt
vol -f memory.raw windows.psscan > psscan.txt
diff pslist.txt psscan.txt
vol -f memory.raw windows.callbacks
vol -f memory.raw windows.ssdt
vol -f memory.raw windows.driverscan
vol -f memory.raw windows.driverirp
Credential Extraction
vol -f memory.raw windows.hashdump
vol -f memory.raw windows.lsadump
vol -f memory.raw windows.cachedump
YARA Integration
Writing Memory YARA Rules rule Suspicious_Injection
{
meta:
description = "Detects common injection shellcode"
strings:
// Common shellcode patterns
$mz = { 4D 5A }
$shellcode1 = { 55 8B EC 83 EC } // Function prologue
$api_hash = { 68 ?? ?? ?? ?? 68 ?? ?? ?? ?? E8 } // Push hash, call
condition:
$mz at 0 or any of ($shellcode*)
}
rule Cobalt_Strike_Beacon
{
meta:
description = "Detects Cobalt Strike beacon in memory"
strings:
$config = { 00 01 00 01 00 02 }
$sleep = "sleeptime"
$beacon = "%s (admin)" wide
condition:
2 of them
}
Scanning Memory
vol -f memory.raw windows.yarascan --yara-rules rules.yar
vol -f memory.raw windows.yarascan --yara-rules rules.yar --pid 1234
vol -f memory.raw windows.yarascan --yara-rules rules.yar --kernel
String Analysis
Extracting Strings
strings -a memory.raw > all_strings.txt
strings -el memory.raw >> all_strings.txt
vol -f memory.raw windows.memmap --pid 1234 --dump
strings -a pid.1234.dmp > process_strings.txt
grep -E "(https?://|[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3})" all_strings.txt
FLOSS for Obfuscated Strings
floss malware.exe > floss_output.txt
floss pid.1234.dmp
Best Practices
Acquisition Best Practices
Minimize footprint : Use lightweight acquisition tools
Document everything : Record time, tool, and hash of capture
Verify integrity : Hash memory dump immediately after capture
Chain of custody : Maintain proper forensic handling
Analysis Best Practices
Start broad : Get overview before deep diving
Cross-reference : Use multiple plugins for same data
Timeline correlation : Correlate memory findings with disk/network
Document findings : Keep detailed notes and screenshots
Validate results : Verify findings through multiple methods
Common Pitfalls
Stale data : Memory is volatile, analyze promptly
Incomplete dumps : Verify dump size matches expected RAM
Symbol issues : Ensure correct symbol files for OS version
Smear : Memory may change during acquisition
Encryption : Some data may be encrypted in memory
Iron Laws
ALWAYS hash the memory dump immediately after acquisition — memory is volatile and can be challenged in court without a cryptographic integrity record proving the dump was not modified post-capture.
NEVER analyze from the live system that produced the dump — writing analysis tool artifacts to the suspect system contaminates volatile evidence and invalidates forensic chain of custody.
ALWAYS verify the OS profile before running plugins — wrong profile produces silently incorrect results; vol -f memory.raw windows.info must confirm OS version before any plugin output is trusted.
NEVER use a single plugin to confirm a finding — pslist misses DKOM-hidden processes; cross-validate with psscan and pstree before reporting any process as hidden.
ALWAYS work from a forensic copy, never the original dump — all analysis writes output files to the working directory; working on the original risks accidental modification of the evidence artifact.
Anti-Patterns Anti-Pattern Why It Fails Correct Approach Skipping acquisition hash Dump integrity cannot be proven in court or peer review; challenges invalidate all findings Hash immediately: sha256sum memory.raw > memory.raw.sha256 before any analysis Wrong OS profile Incorrect offsets produce garbage output with no error — findings appear valid but are fabricated Run vol -f memory.raw windows.info first; confirm OS version and build before other plugins Analyzing on the live suspect system Tool artifacts contaminate volatile evidence; file timestamps change; live-response tools modify RAM state Acquire dump, transfer to isolated analysis workstation, analyze the copy only Trusting a single plugin DKOM rootkits hide from pslist linked-list traversal but appear in psscan pool scan Cross-validate process lists with at least pslist, psscan, and pstree before reporting Missing timeline correlation Memory artifacts without disk/network context cannot establish causality or attacker timeline Correlate memory findings with event logs and PCAP before writing the incident report
Memory Protocol (MANDATORY) Before starting:
Read .claude/context/memory/learnings.md
New pattern -> .claude/context/memory/learnings.md
Issue found -> .claude/context/memory/issues.md
Decision made -> .claude/context/memory/decisions.md
ASSUME INTERRUPTION: If it's not in memory, it didn't happen.