PowerShell Service Persistence via Registry ImagePath on Windows

Flags Windows registry service ImagePath entries that reference PowerShell (powershell/pwsh).

FreeReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
oscd.community, Natalia Shornikova (SigmaHQ), DRL 1.1
Published
2020-10-06
Updated
2026-07-30

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

This rule identifies attempts to persist PowerShell by writing a registry service entry where the service ImagePath contains powershell or pwsh. Attackers may use this technique to launch PowerShell automatically via the Windows Service mechanism. It relies on Windows registry set telemetry capturing the TargetObject path under \Services\ and the ImagePath content in Details.

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 Service Persistence via Registry ImagePath on Windows
Pivot detection · T1569.002 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.