Vai al contenuto
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 e threat hunting

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

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
ujeTereQ/+…Z1rmshDQ==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchettoe8569667…c215809c
e8569667ed32…a3c2c215809c4 file · ⁦3.4 KB⁩
ScansioneMedio2 segnalazioni
  • Script eseguibile incluso nella skillscripts/analyst.py
  • Link a domini esterni
Vedi la scansione completa
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.

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).

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellSìSì
Usa la reteSìSì
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

  1. MediaFile · Script eseguibile incluso nella skillscripts/analyst.py
  2. InfoLink · Link a domini esterni

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v1.0.013 nov 2026da7600ae8569667Firmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login