Windows: Service Created by System Using Client with PID 0 (SCM Event 7045)

Alerts on Windows service installation events (SCM EventID 7045) where the client process ID is 0.

FreeReviewedSigma · High · v2
Product
windows
Service
system
Author
Tim Rauch (Nextron Systems), Elastic (idea) (SigmaHQ), DRL 1.1
Published
2022-09-15
Updated
2026-07-31

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags Windows service creation events from the Service Control Manager (EventID 7045) when the recorded client process has PID 0. An attacker may attempt to obscure the origin of service installation by using anomalous process identifiers. The detection relies on Windows service installation telemetry, specifically the SCM provider event fields capturing the client ProcessId value.

Related detections9 linkedT1543 — drag to rearrange
Suspicious GitHub Actions Runner In Hidden Directory via Shell (via process_creation)
Suspicious Self-Hosted GitHub Actions Runner Started As Root via Shell (via process_creation)
Suspicious GitHub Self-Hosted Runner Registration via Audit Log (via github)
Malicious Fire Ant Hypervisor Backdoor Artifacts on ESXi and vCenter (via file_event)
Suspicious D-Bus System Service Persistence File Creation
Malicious BRICKSTORM Backdoor Execution via Masqueraded Binary Path
Suspicious SonicWall SMA init.d Persistence Launching deploy_new.py
Malicious Linux XorDDoS gcc.pid Device Marker File via file_event
Windows Code Integrity: Blocked Driver Load Due to Revoked Certificate (Event ID 3023)
Windows: Service Created by System Using Client with PID 0 (SCM Event 7045)
Pivot detection · T1543 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. 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.