skills/blue-team/memory-forensics/SKILL.md
Analyzes volatile memory dumps to detect malware, rootkits, and security breaches in digital forensics.
npx skillsauth add alphaonedev/openclaw-graph memory-forensicsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill enables analysis of volatile memory dumps using tools like Volatility to identify malware, rootkits, and security breaches, supporting digital forensics investigations.
Use this skill during incident response for suspected breaches, when analyzing RAM dumps from compromised systems, or for proactive security assessments on endpoints with potential malware infections.
Invoke this skill via CLI commands in a Python script or directly in a terminal. Always specify the memory dump file and required plugins. For automation, wrap commands in a function that handles file paths and outputs. Use environment variables for API keys if extending to cloud-based forensics tools.
Example pattern in Python:
import subprocess
dump_file = 'memory.dmp'
subprocess.run(['volatility', '-f', dump_file, 'pslist'])
Use Volatility framework commands for core functionality. Set the VOLATILITY_PROFILE env var for profile mismatches, e.g., $VOLATILITY_PROFILE=Win7SP1x64.
volatility -f memory.dmp imageinfo — Identifies the OS profile from the dump.
-f for file path, --profile=Win10x64 to override auto-detection.volatility -f memory.dmp malfind — Scans for injected code or malware hooks.
volatility -f memory.dmp malfind > malware_output.txtfrom volatility3.framework import interfaces, then call interfaces.configuration.ConfObject() for configurations.
from volatility3 import framework
config = framework.require_plugin('windows').build_configuration()
config['primary'] = 'memory.dmp'
{"plugin": "pslist", "dumpfile": "memory.dmp"} for custom runs.Integrate by installing Volatility via pip (pip install volatility), then call from scripts. For authentication in cloud forensics (e.g., AWS Memory DB analysis), use env vars like $AWS_ACCESS_KEY_ID and $AWS_SECRET_ACCESS_KEY. Ensure the skill runs in a isolated environment to avoid contamination; pass dump files via secure paths. For multi-tool integration, chain with tools like strings or YARA by piping outputs, e.g., volatility -f memory.dmp strings | grep suspicious.
Handle common errors by checking Volatility's exit codes; e.g., if profile not found, use imageinfo first. For file not found errors, validate paths before running. In scripts, wrap commands in try-except blocks:
try:
result = subprocess.run(['volatility', '-f', 'memory.dmp', 'pslist'], capture_output=True, check=True)
except subprocess.CalledProcessError as e:
print(f"Error: {e.returncode} - {e.stderr.decode()}")
Log detailed errors for debugging, and use $VOLATILITY_DEBUG=1 env var to enable verbose output.
volatility -f infected.dmp --profile=Win10x64 malfindvolatility -f infected.dmp imageinfo to confirm profile, then analyze output for PID and virtual address of suspicious processes.volatility -f linux.dmp linux_pslistlinux_modules to spot discrepancies, then use strings on flagged addresses for further inspection.tools
Root web development: project structure, tooling selection, deployment decisions
development
WebAssembly: Rust/Go/C to WASM, wasm-bindgen, Emscripten, WASM Component Model
development
Vue 3: Composition API script setup, Pinia, Vue Router 4, SFCs, Vite, Nuxt 3
tools
Tailwind CSS 4: utility classes, config, JIT, arbitrary values, darkMode, plugins, shadcn/ui