Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
meltedinhex/detecting-process-injection-in-memoryReporting and compliance

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-memory

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
p1TcTkqp3O…D02E6HDQ==The CLI checks the SHA-256 and the signature before it writes a file.
Package44942cd8…6903790c
44942cd83c5a…53d46903790c4 files · ⁦3.0 KB⁩
ScanMedium2 findings
  • Executable script shipped with the skillscripts/analyst.py
  • Links to outside domains
See the full scan
Sourcegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/detecting-process-injection-in-memory@da7600a

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

bash
vol -f memory.raw windows.malfind > malfind.txt

Step 2: Score injection candidates

bash
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 program signature.
  • 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 for the scorer.
  • ATT&CK T1055 and Volatility 3 docs (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesYesYes
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumFile · Executable script shipped with the skillscripts/analyst.py
  2. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v1.0.0Nov 13, 2026da7600a44942cd8Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login