In-Memory gpupdate Spawned by Unusual Parent as Cobalt Strike Sacrificial Process (via process_creation)

PremiumReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-11-10
Updated
2026-11-10

ATT&CK techniques

Priv Esc → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects gpupdate.exe launched by a parent other than the expected Group Policy scheduling processes, the sacrificial spawnto behavior used in the Nitrogen campaign to host injected Cobalt Strike beacon code. Adversaries leverage a benign system binary as an injection target to blend beacon execution into normal activity, making detection useful for surfacing process injection.

Related detections9 linkedT1055.001 — drag to rearrange
In-Memory Remote Thread Created With a Library-Loading Start Address (via create_remote_thread)
Suspicious AppInit_DLLs Registry Modification for DLL Injection
Malicious DLL Injection via Mavinject Process Creation
Suspicious Process Injection via mavinject INJECTRUNNING
In-Memory Process Injection via Mavinject INJECTRUNNING (via process_creation)
Suspicious Service Reconfiguration of SessionEnv or IKEEXT for DLL Injection by EAGERBEE
Windows Process Creation: Renamed Mavinject32/64.EXE Execution
Windows Process Injection via Mavinject Using INJECTRUNNING Flag
Windows Process Execution and DLL Injection via Tracker.exe
In-Memory gpupdate Spawned by Unusual Parent as Cobalt Strike Sacrificial Process (via process_creation)
Pivot detection · T1055.001 · 9 related

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