Windows Process Creation: PowerShell ExecutionPolicy Set to Bypass/Unrestricted

Alerts on PowerShell started with -ExecutionPolicy set to Bypass/Unrestricted, indicating a potentially insecure script execution posture.

FreeReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
frack113 (SigmaHQ), DRL 1.1
Published
2021-11-01
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 flags Windows process creation events where PowerShell (PowerShell.exe, pwsh.exe, or PowerShell ISE) is launched with execution policy arguments indicating an insecure state such as -ExecutionPolicy Bypass or Unrestricted. Attackers may use this to weaken script execution restrictions and run malicious or unsigned PowerShell content. The detection relies on process creation telemetry, matching PowerShell-related image names and specific command-line substrings containing execution policy values.

Related detections9 linkedT1059.001 — drag to rearrange
Suspicious Node.js Spawning Script Interpreter for Dropped Payload
Suspicious PowerShell Remote Download and Execution via Invoke-WebRequest
Suspicious Script Host Spawning Hidden PowerShell (via process_creation)
Suspicious PowerShell Reflective Assembly Load With GZip Decompression (via process_creation)
Suspicious PowerShell Invoke-Expression with Replace Obfuscation
Suspicious PowerShell Archive Extraction to AppData Roaming
Malicious PowerShell Spawned by Masqueraded NVIDIA GeForce Experience Binary
Suspicious PowerShell Hidden Unrestricted Execution via ClickFix
Suspicious PowerShell Spawned by cscript in Script Chain
Windows Process Creation: PowerShell ExecutionPolicy Set to Bypass/Unrestricted
Pivot detection · T1059.001 · 9 related

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