Windows Process Creation: Executable Image Missing Absolute Path (Possible Process Ghosting)

Flags Windows process creation where the executable Image lacks an absolute path, potentially indicating process ghosting.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Max Altgelt (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-12-09
Updated
2026-07-30

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 Windows process creation events where the Image field does not contain a backslash, indicating the executable path is not absolute and may not exist on disk when logged. Attackers can use process-ghosting or other non-standard process creation techniques to create processes whose executable image is obscured or missing. The detection relies on process creation telemetry fields for Image and CommandLine values to identify cases that match the rule’s excluded/allowed patterns.

Related detections9 linkedT1055 — drag to rearrange
Malicious AddInProcess32 Network Beacon on PureRAT C2 Ports
Suspicious Payload Staging in ProgramData IntelDriver Folder (via file_event)
Possible DarkGate Process Injection via iTunesHelper Spawning vbc.exe
Suspicious PowerShell Shellcode Loader via Function Pointer Delegate
Suspicious Named Pipe Created by Kazuar Backdoor for Interprocess Command Channel
Suspicious SmallTiger Backdoor DLL Load via Image Load
Suspicious svchost Execution With Anomalous Arguments via DeedRAT (via process_creation)
Suspicious Sang Loader Execution with Install or PassUAC Arguments
Suspicious GodRAT Shellcode Injection via Puppet Argument (via process_creation)
Windows Process Creation: Executable Image Missing Absolute Path (Possible Process Ghosting)
Pivot detection · T1055 · 9 related

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