PowerShell ExecutionPolicy Set to Bypass via Registry (via registry_set)

PremiumReviewedSigma · Medium · v1
Product
windows
Category
registry_set
Author
HuntRule
Published
2026-11-11
Updated
2026-11-11

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 detects the PowerShell ExecutionPolicy registry value being set to Bypass or Unrestricted, the persistent policy weakening described in the STRT registry-abuse research that lets unsigned scripts run without prompts. Adversaries leverage this registry change so their scripts execute freely across sessions, so this behavior warrants review against expected administrative configuration.

Related detections9 linkedT1059.001 — drag to rearrange
Malicious Fickle Stealer Remote PowerShell Execution From UNC Share (via process_creation)
Suspicious PDF Editor Updater Binary Spawning PowerShell (via process_creation)
Malicious XWorm Script Chain Execution from ProgramData Music Visuals Directory (via process_creation)
Scheduled task executing powershell encoded payload from registry
Malicious Paper Werewolf PowerShell Loader Spawned by Excel via XLL Add-In (via process_creation)
PowerShell Alias Obfuscation Resolving iex and Invoke-RestMethod via ClickFix (via process_creation)
ClickFix PowerShell Download Cradle Launched From Run Dialog (via process_creation)
SharePoint IIS Worker Process Spawning PowerShell With Encoded Command (via process_creation)
In-Memory Phantom Stealer In-Memory Process Injection via PowerShell Add-Type API Chain (via ps_script)
PowerShell ExecutionPolicy Set to Bypass via Registry (via registry_set)
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.