huntrule

PowerShell Script Execution via Windows Service Creation (Service Control Manager)

Flags service creation/start events where the service ImagePath references PowerShell (powershell/pwsh).

FreeReviewedSigma · High · v2
Product
windows
Service
system
Author
oscd.community, Natalia Shornikova (SigmaHQ), DRL 1.1
Published
2020-10-06
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Execution

  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

Identifies Windows Service creation events where the service ImagePath contains PowerShell executables (powershell.exe or pwsh). Creating a service to run a script can provide persistence and allow attackers to execute commands outside normal interactive sessions. Detection relies on System/Service Control Manager event telemetry, specifically EventID 7045, and matches the ImagePath content for PowerShell-related binaries.

Reporting behind it

Related detections9 linkedT1569.002 — drag to rearrange
Suspicious PsExec Service Named Sliver
PsExec Remote Service Execution on Target Host (via process_creation)
Renamed Procdump Tool Used for Dumping LSASS Process (via process_creation)
Suspicious Service Installation Masquerading as winupd
Suspicious PSexec Application Execution (via process_creation)
Malicious Metasploit PsExec Named Pipe Command Execution
Malicious PsExec Service Installation via PSEXESVC
Malicious NotPetya Payload Execution via Rundll32 Ordinal Export from Windows Directory
Suspicious Lateral Movement via PsExec Service (via process_creation)
PowerShell Script Execution via Windows Service Creation (Service Control Manager)
Pivot detection · T1569.002 · 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.