Operator On The Wire
Join
← Back to Knowledge Base
BLUE TEAM / THREAT HUNT / WINDOWS / EXECUTION

Process Injection

This note documents detection patterns related to Process Injection within Windows environments.


Direct Indicators

LogEvent IDMeaningForensic ValueNotes
Sysmon8CreateRemoteThreadCriticalStrong direct indicator of remote thread injection.
Sysmon10Process accessCriticalDetects suspicious handle access before injection.
Sysmon1Process creationCriticalRequired to identify injector lineage.
Security4688Process creationHighParent-child context for injector process.
Sysmon7Image loadedHighDLL loads may support injection chain.
Sysmon11File createMediumPayload staging before injection.
Security4673Sensitive privilege use attemptedHighSeDebugPrivilege often precedes injection.

Indirect Indicators

IndicatorWhat To Look ForForensic ValueNotes
High-rights handle to foreign processPROCESS_VM_WRITE, PROCESS_CREATE_THREADCriticalCore injection precursor.
Unsigned process touches signed processTemp/AppData injector to system processCriticalStrong malicious signal.
Explorer / Office injects into system binaryRare lineageCriticalHighly suspicious.
Remote thread into browser or lsassCommon target choiceCriticalCredential theft or stealth.
Memory-only child behaviorNetwork activity without disk payloadHighFileless clue.
Process starts then no file writesIn-memory executionHighCommon injection outcome.

Common Tools

ToolUsage
mimikatzInjection modules
Cobalt StrikeBeacon injection
Process HackerManual injection
rundll32.exeDLL staging
PowerShellReflective loaders
custom loadersRemote thread injection

Relevant Artifacts

  • Sysmon Event IDs 8, 10, 1, 7
  • Security Event IDs 4688, 4673
  • Prefetch for injector binary
  • Amcache / ShimCache
  • EDR memory telemetry
  • Handle access records
  • MFT / USN if payload staged first

MITRE ATT&CK References

  • T1055 Process Injection
  • T1055.001 Dynamic-link Library Injection
  • T1055.002 Portable Executable Injection

Decision Tree

  1. Which process opened target?

    • Source image
    • Signed status
  2. Granted access suspicious?

    • VM_WRITE
    • CREATE_THREAD
  3. Remote thread created?

    • Sysmon 8
    • Target process
  4. Target sensitive?

    • lsass
    • explorer
    • browser
    • svchost
  5. Expand:

    • Memory-only payload
    • Network from target
    • Parent chain
  6. Scope:

    • Single target
    • Multiple injections
    • Shared injector

Example Detection Templates

KQL

Sysmon
| where EventID == 8
| project TimeGenerated, Computer, SourceImage, TargetImage
Sysmon
| where EventID == 10
| where GrantedAccess has_any ("0x1fffff","0x1f3fff","0x143a")
| project TimeGenerated, Computer, SourceImage, TargetImage, GrantedAccess

EQL

process where event.code == "8"
sequence by host.name with maxspan=5m
  [ process where event.code == "10" ]
  [ process where event.code == "8" ]

Sigma

title: Process Injection Detection
id: 2d5f3c90-process-injection
status: experimental
description: Detects remote thread creation and suspicious process access
references:
  - https://attack.mitre.org/
author: Vergil
date: 2026-03-07
logsource:
  product: windows
  service: sysmon
detection:
  selection:
    EventID:
      - 8
      - 10
  condition: selection
fields:
  - SourceImage
  - TargetImage
  - GrantedAccess
falsepositives:
  - Security tooling
level: high
tags:
  - attack.defense_evasion
  - attack.t1055

Mitigation & Hardening

Control AreaMitigationEffectivenessNotes
Sysmon Event 8/10Enable injection telemetryCriticalCore visibility
EDR memory analyticsMonitor thread anomaliesCriticalBest detection source
Protect high-value processesLSASS / browser hardeningHighReduce target abuse
Restrict SeDebugPrivilegeMinimize debug rightsHighReduce injection surface
Application controlBlock unsigned injectorsHighPrevent common loaders