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

ATT&CK techniques

Execution
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. 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.

Related detections9 linkedT1569.002 — drag to rearrange
Suspicious Executable Launched from Public Music Staging Directory (via process_creation)
Malicious Service Execution via PAExec
Suspicious RemCom Service Named Pipe for Lateral Movement (via pipe_created)
Malicious CACTUS Ransomware Deployment via TotalExec Script (via ps_script)
Malicious PsExec Service Binary Execution from Windows Directory via services.exe (via process_creation)
Malicious Remote Command Execution via smbexec Output Redirection Pattern
Malicious Lateral Movement via PsExec File-List Target
Malicious PsExec SYSTEM Interactive Shell Execution (via process_creation)
Suspicious PsExec Service Named Sliver
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.