Skip to content

meltedinhex/analyst-ai-pack / skills/hunting-process-injection-with-sysmon

hunting-process-injection-with-sysmon

Verified

Hunts for process injection using Sysmon telemetry: correlating CreateRemoteThread (EID 8), suspicious cross-process access (EID 10), and RWX image-less memory to surface hollowing, shellcode injection, and APC abuse. Activates for requests to hunt process injection, analyze Sysmon EID 8/10, or detect code injection on Windows.

FileKindSize
LICENSEother340 B
SKILL.mdskill md3.3 KB
references/api-reference.mdmarkdown1.3 KB
scripts/analyst.pyscript3.0 KB

references/api-reference.md

View on GitHub
# API Reference: Hunting Process Injection with Sysmon

## Overview

`scripts/analyst.py` triages normalized Sysmon events (Event ID 8 CreateRemoteThread, Event ID 10
ProcessAccess), correlating source→target pairs, weighting high-power access masks and
script/macro-spawned sources, and returning ranked injection candidates. It reads local JSON
only.

## Dependencies

| Package | Version | Purpose |
|---------|---------|---------|
| (stdlib) | — | JSON, file IO |

## Input format

```json
[
  {"event_id": 10, "source_image": "C:/a.exe", "target_image": "C:/Windows/explorer.exe",
   "target_pid": 1234, "granted_access": "0x1F0FFF", "source_parent_image": "powershell.exe"},
  {"event_id": 8, "source_image": "C:/a.exe", "target_image": "C:/Windows/explorer.exe",
   "target_pid": 1234}
]
```

## Core functions

### `triage(events)`
Aggregates events by (source, target, pid), scores injection likelihood, and returns candidates
scoring >= 50.

## Usage

```bash
python scripts/analyst.py triage sysmon.json
```

## Sources

- Sysmon documentation (Event IDs 8 and 10) —
  https://learn.microsoft.com/sysinternals/downloads/sysmon
- MITRE ATT&CK T1055 Process Injection — https://attack.mitre.org/techniques/T1055/
- CAR-2019-04-001 (CreateRemoteThread detection analytic) — MITRE Cyber Analytics Repository
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall