huntrule

Windows Service Installation via Scripted ImagePath Indicators (Event 7045)

Identifies suspicious Windows service installations that embed script host execution via Event ID 7045 ImagePath patterns.

FreeReviewedSigma · High · v2
Product
windows
Service
system
Author
pH-T (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-03-18
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 Windows service creation events (Service Control Manager, EventID 7045) where the service ImagePath contains specific command-line flags and script or scripting host binaries. Attackers often abuse service installation for persistence and privilege escalation by registering a service that executes scripts or scriptable interpreters. The detection relies on Windows service installation telemetry that records the Provider_Name and the ImagePath content from Event 7045.

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 Installation via Scripted ImagePath Indicators (Event 7045)
Pivot detection · T1543.003 · 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.