huntrule

Windows Service Control Manager: WerFaultSvc Installed via Service Creation (Event ID 7045)

Alerts on Windows Event 7045 service creation for "WerFaultSvc" as an indicator of dropper-style persistence.

FreeReviewedSigma · Critical · v5
Product
windows
Service
system
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2018-11-23
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Persistence → Priv Esc

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags creation or installation events where the Service Control Manager reports ServiceName "WerFaultSvc" in a Windows system service event with Event ID 7045. Attackers may abuse service creation to gain persistence or elevate execution by registering their payload as a Windows service. The detection relies on Windows System logs from the Service Control Manager, specifically the service name and Event ID fields.

Reporting behind it

Related detections9 linkedT1543.003 — drag to rearrange
Malicious Service Created With Binary Path in ProgramData
Malicious Abyss Locker wmihelper SSH Backdoor Deployment (via file_event)
Malicious AuKill EDR Killer Kernel Driver Load via Process Explorer Driver (via image_load)
Suspicious TermService ServiceDll Hijack via Registry (via registry_set)
Suspicious Service Creation Named RDP-Controller via sc.exe (via process_creation)
Suspicious Service or Task Named windowsinspectionupdate (via process_creation)
Malicious Service Persistence via sc.exe Creating msdnetsvc
Suspicious Stately Taurus Masqueraded Service and Task Persistence via process_creation
Malicious Vulnerable Driver Load for EDR Evasion (via image_load)
Windows Service Control Manager: WerFaultSvc Installed via Service Creation (Event ID 7045)
Pivot detection · T1543.003 · 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.