Install
$ agentstack add skill-meltedinhex-analyst-ai-pack-detecting-process-injection-in-memory ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Detecting Process Injection in Memory
When to Use
- You have a Windows memory image and want to find injected/hollowed code.
- You are triaging private RWX regions, unbacked executable memory, and PE headers in private
allocations (classic injection/hollowing signs).
Do not use this on a live production host without authorization — work from an acquired image. This skill interprets analysis output; run Volatility separately on the image.
Prerequisites
- A memory image and Volatility 3 (
windows.malfind,windows.vadinfo) installed.
Safety & Handling
- Treat carved injected regions as live malicious code; store them password-protected.
Workflow
Step 1: Run malfind and capture output
vol -f memory.raw windows.malfind > malfind.txt
Step 2: Score injection candidates
python scripts/analyst.py score malfind.txt
Flags regions with PAGE_EXECUTE_READWRITE, MZ/PE headers in private memory, and shellcode-like disassembly hints, ranking processes by suspicion.
Step 3: Corroborate
Cross-check flagged PIDs with windows.vadinfo (private, executable, no mapped file) and the process tree for anomalous parents.
Step 4: Carve and route
Carve the injected region for follow-on shellcode/PE recovery and analysis.
Validation
- Flagged regions are private + executable, not legitimate mapped images.
- PE-in-private-memory findings are confirmed by an MZ/
This programsignature. - High-scoring PIDs corroborate with VAD protections and process-tree anomalies.
Pitfalls
- JIT engines (.NET, Java, browsers) legitimately create RWX regions — corroborate before alerting.
- Relying on malfind alone; pair with vadinfo and ldrmodules.
- Missing hollowing where the region is RX (not RWX) after protection change.
References
- See [
references/api-reference.md](references/api-reference.md) for the scorer. - ATT&CK T1055 and Volatility 3 docs (linked in frontmatter).
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: meltedinhex
- Source: meltedinhex/analyst-ai-pack
- License: Apache-2.0
- Homepage: https://meltedinhex.com/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.