hunting-process-injection-with-sysmon
Hunts for process injection using Sysmon telemetry: correlating CreateRemoteThread
v1.0.03 installazioni+3 in 7 giorni24 StelleApache-2.0sincronizzato 10 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/hunting-process-injection-with-sysmonScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchettoe8569667…c215809c
e8569667ed32…a3c2c215809c4 file · 3.4 KBScansioneMedio2 segnalazioni
- Script eseguibile incluso nella skillscripts/analyst.py
- Link a domini esterni
Sorgentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/hunting-process-injection-with-sysmon@da7600a
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
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).
python scripts/analyst.py triage sysmon.jsonStep 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.mdfor the Sysmon triage helper. - Sysmon docs and ATT&CK T1055 (linked in frontmatter).
File di questa versione
references/11.3 KB
- api-reference.md1.3 KB
scripts/13.0 KB
- analyst.py3.0 KB
- LICENSE340 B
- SKILL.md3.3 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | Sì | Sì |
| Usa la rete | Sì | Sì |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
- MediaFile · Script eseguibile incluso nella skillscripts/analyst.py
- InfoLink · Link a domini esterni
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v1.0.0 | 13 nov 2026 | da7600a | e8569667 | Firmata | – |
Altro da meltedinhex
Tutto da questo editore- 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
Altro in DFIR e threat hunting
Vai alla categoria- hunting-for-command-and-control-beaconingmukul975/hunting-for-command-and-control-beaconing5
- audit-context-buildingtrailofbits/audit-context-building4
- incident-response-forensicssecurityskills/incident-response-forensics3
- extracting-credentials-from-memory-dumpmukul975/extracting-credentials-from-memory-dump3
- analyzing-browser-forensics-with-hindsightmukul975/analyzing-browser-forensics-with-hindsight3
- forensics-ctfaeondave/forensics-ctf3
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login