Windows Process Creation: Executable Launches Identical Self Instance (Sacrificial Process)

Alerts on Windows process creation where a targeted parent context suggests an executable spawns an identical instance, potentially as a sacrificial process.

FreeReviewedSigma · Low · v5
Product
windows
Category
process_creation
Author
frack113 (SigmaHQ), DRL 1.1
Published
2025-10-17
Updated
2026-07-31

ATT&CK techniques

Priv Esc → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags process creation events where a parent process image matches an identical/same executable instance, a pattern that can be used to spawn a sacrificial process for stealth and evasion. Attackers may leverage this to support code injection or to manipulate execution flow, often accompanied by suspicious command-line behavior and process ancestry. Telemetry relies on Windows process creation fields, including parent image and executable attributes, with additional filtering to reduce matches from common legitimate installers and tools.

Related detections9 linkedT1055 — drag to rearrange
Suspicious Office Application Spawning Script Or Shell Interpreter
Suspicious Network Connection From wabmig.exe (Turian Injection)
Suspicious Outbound Network Connection from Explorer Process
Suspicious AppLaunch.exe Spawned As Injection Target (via process_creation)
Suspicious BugSleep Marker File in Public Directory
Suspicious CRAT Injection Named Pipe ChromeUpdatePipe (via pipe_created)
AsyncRAT Injector libPK.dll Written to Public Folder (via file_event)
FlawedGrace spawning threat injection target
In-Memory Ramnit Process Injection Target Spawned by WmiPrvSE in drIBAN Fraud Operation (via process_creation)
Windows Process Creation: Executable Launches Identical Self Instance (Sacrificial Process)
Pivot detection · T1055 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.