Windows Process Creation: PowerShell Command Lines with Hidden Base64-Encoded Keywords

Alerts on PowerShell launching with 'hidden' and embedded base64-like strings in the command line.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
John Lambert (rule) (SigmaHQ), DRL 1.1
Published
2019-01-16
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) is launched with a command line containing the substring ' hidden ' and includes one or more long base64-like strings. Such obfuscation is commonly used to conceal PowerShell keywords and payload content from straightforward command-line inspection. The detection relies on process creation telemetry, including the executable path/name and the full command line.

Related detections9 linkedT1059.001 — drag to rearrange
Suspicious Script Interpreter Spawned by Explorer via ClickFix Run Dialog (via process_creation)
Suspicious PowerShell Download Cradle via ClickFix Fake CAPTCHA (via process_creation)
Suspicious PowerShell EncodedCommand Spawned From Command Shell via Process Creation
Suspicious Script Download via Curl and PowerShell by Dohdoor
Malicious Mass Hyper-V Virtual Machine Shutdown via PowerShell by Kraken Ransomware
Suspicious PowerShell WebClient DownloadFile of Archive Payload (UAT-7237)
Suspicious SharePoint Worker Process Spawning Command Interpreter via ToolShell
Malicious Emmenhtal JavaScript Loader Spawning Encoded PowerShell
Suspicious Python Interpreter Launching Encoded PowerShell via subprocess
Windows Process Creation: PowerShell Command Lines with Hidden Base64-Encoded Keywords
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.