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/hunting-process-injection-with-sysmonDFIR and threat hunting

hunting-process-injection-with-sysmon

⁨Hunts for process injection using Sysmon telemetry: correlating CreateRemoteThread⁩

v1.0.03 installs+3 in 7 days24 StarsApache-2.0synced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install meltedinhex/hunting-process-injection-with-sysmon

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

SignatureSigned, ed25519
ujeTereQ/+…Z1rmshDQ==The CLI checks the SHA-256 and the signature before it writes a file.
Packagee8569667…c215809c
e8569667ed32…a3c2c215809c4 files · ⁦3.4 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/hunting-process-injection-with-sysmon@da7600a

When to Use

  • You have Sysmon (or equivalent EDR) telemetry and want to hunt code injection across hosts.
  • You are testing a hypothesis that an implant injects into benign processes (explorer.exe, svchost.exe) to evade defenses.
  • You need to triage EID 8/10 events into a prioritized list of injection candidates.

Do not use EID 8/10 in isolation as a verdict — legitimate software (security tools, debuggers, injectors in dev tools) generates these; correlation and baselining are required.

Prerequisites

  • Sysmon configured to log Event ID 8 (CreateRemoteThread) and 10 (ProcessAccess) with useful access masks; a SIEM or log export to query.
  • A baseline of normal cross-process access for your environment.

Workflow

Step 1: Pull the candidate events

Collect EID 8 (remote thread creation) and EID 10 (process access) with high-power access masks (e.g., 0x1F0FFF, PROCESS_VM_WRITE | PROCESS_CREATE_THREAD).

Step 2: Filter known-good

Remove baseline noise: security agents, legitimate debuggers, and known injector pairs. Keep unusual source→target pairs (e.g., a document app injecting into a browser).

bash
python scripts/analyst.py triage sysmon.json

Step 3: Correlate signals

Raise priority when multiple indicators stack: cross-process write + remote thread into the same target, target with RWX private memory, or source process spawned from a macro/script.

Step 4: Pivot per candidate

For top candidates, pull the source process tree, image path, signing status, and network connections to confirm or clear.

Step 5: Confirm and respond

Validate suspected hollowing/shellcode (memory analysis), then escalate confirmed injections to IR and convert the logic into a detection rule.

Validation

  • Surfaced candidates show a coherent injection pattern (access + remote thread to same PID), not isolated single events.
  • Known-good injectors are filtered, keeping the candidate list small and reviewable.
  • Confirmed cases are corroborated by process lineage or memory evidence.

Pitfalls

  • Alerting on every EID 10 — the access mask matters; filter to write/inject rights.
  • Ignoring source lineage; a script-spawned source is far more suspicious.
  • No baseline, so security tooling buries real injection in noise.

References

  • See references/api-reference.md for the Sysmon triage helper.
  • Sysmon docs and ATT&CK T1055 (linked in frontmatter).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
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, 2026da7600ae8569667Signed–

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