memory-forensics-process-and-injection-analysis — Claude Code skill
memory-forensics-process-and-injection-analysis is a Claude Code skill for examining Windows processes and possible code injection in memory dumps. It activates for work on hidden processes, altered images, and suspicious memory regions.
no license ★ 73 updated 2026-11-15
npx skills add W4L33Dx/Cyber-Monster --skill memory-forensics-process-and-injection-analysis -a claude-codeWhat memory-forensics-process-and-injection-analysis does
The skill guides an analysis of Windows processes and possible code injection in memory captures. It compares process and loader records with virtual memory regions to surface hidden modules, signs of process replacement, and executable areas that warrant investigation.
Its workflow uses Volatility plugins such as windows.pslist, windows.psscan, and windows.malfind. If a plugin name does not resolve, it suggests trying the windows.malware.* namespace. For an image, windows.info must resolve the kernel base first. Minidumps and crash dumps can lack much of the user-mode memory, so conclusions from them are limited to process metadata.
What it helps with
- locate processes missing from the regular process list
- compare loader module records with mapped memory
- spot executable regions that may contain injected code
- check a process image for signs of replacement
Example prompts for the agent
- Inspect this Windows memory dump for hidden processes and possible injected code.
- Compare the process module lists with memory regions and report discrepancies.
- Check this dump for signs that a process image was replaced.
How to install memory-forensics-process-and-injection-analysis
1Skills CLI (Vercel)
npx skills add W4L33Dx/Cyber-Monster --skill memory-forensics-process-and-injection-analysis -a claude-code2Manually: put the files in place
~/.claude/skills/memory-forensics-process-and-injection-analysis/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/memory-forensics-process-and-injection-analysis/
1Skills CLI (Vercel)
npx skills add W4L33Dx/Cyber-Monster --skill memory-forensics-process-and-injection-analysis -a codex2Manually: put the files in place
.agents/skills/memory-forensics-process-and-injection-analysis/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add W4L33Dx/Cyber-Monster --skill memory-forensics-process-and-injection-analysis -a cursor2Manually: put the files in place
.cursor/skills/memory-forensics-process-and-injection-analysis/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install W4L33Dx/Cyber-Monster blue-team/digital-forensics/memory-forensics-process-and-injection-analysis2Manually: put the files in place
.github/skills/memory-forensics-process-and-injection-analysis/SKILL.md1Skills CLI (Vercel)
npx skills add W4L33Dx/Cyber-Monster --skill memory-forensics-process-and-injection-analysis -a gemini-cli2Platform CLI
gemini skills install https://github.com/W4L33Dx/Cyber-Monster --path blue-team/digital-forensics/memory-forensics-process-and-injection-analysisManually: put the files in place
.devin/skills/memory-forensics-process-and-injection-analysis/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about memory-forensics-process-and-injection-analysis
How do I install memory-forensics-process-and-injection-analysis in Claude Code?
Run npx skills add W4L33Dx/Cyber-Monster --skill memory-forensics-process-and-injection-analysis -a claude-code. The skill file is at ~/.claude/skills/memory-forensics-process-and-injection-analysis/SKILL.md.
What does memory-forensics-process-and-injection-analysis do?
It examines Windows processes and memory regions to identify hidden modules, possible process replacement, and signs of code injection.
What does memory-forensics-process-and-injection-analysis need to work?
For an image, windows.info must resolve the kernel base. The workflow uses Volatility plugins; minidumps and crash dumps may not contain enough user-mode memory for that part of the analysis.