detecting-process-injection-in-memory
Detects process injection in a memory image by identifying private executable regions
v1.0.02 installs+2 in 7 days24 StarsApache-2.0synced 11 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/detecting-process-injection-in-memoryWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package44942cd8…6903790c
44942cd83c5a…53d46903790c4 files · 3.0 KBScanMedium2 findings
- Executable script shipped with the skillscripts/analyst.py
- Links to outside domains
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/detecting-process-injection-in-memory@da7600a
On this page
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.txtStep 2: Score injection candidates
python scripts/analyst.py score malfind.txtFlags 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.mdfor the scorer. - ATT&CK T1055 and Volatility 3 docs (linked in frontmatter).
Files in this version
references/11.2 KB
- api-reference.md1.2 KB
scripts/12.6 KB
- analyst.py2.6 KB
- LICENSE340 B
- SKILL.md2.8 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | Yes | Yes |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumFile · Executable script shipped with the skillscripts/analyst.py
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v1.0.0 | Nov 13, 2026 | da7600a | 44942cd8 | Signed | – |
More from meltedinhex
All from this publisher- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-sigma-detection-rulesmeltedinhex/writing-sigma-detection-rules3
More in Reporting and compliance
See the category- skillduty1g/skill5
- rea-ci-tests-auditmorluto/rea-ci-tests-audit4
- tracking-threat-actor-infrastructuremukul975/tracking-threat-actor-infrastructure4
- performing-authenticated-scan-with-openvasmukul975/performing-authenticated-scan-with-openvas4
- slicing-code-contexttrailofbits/slicing-code-context4
- 1337aeondave/13374
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login