Windows Process Creation: Cmd Invokes PowerShell via Obfuscated Environment Variable Expansion

Alerts on cmd.exe command lines that use obfuscated environment-variable SET to execute PowerShell.

FreeReviewedSigma · High · v2
Product
windows
Category
process_creation
Author
Jonathan Cheong, oscd.community (SigmaHQ), DRL 1.1
Published
2020-10-15
Updated
2026-07-31

ATT&CK techniques

Execution → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags Windows command interpreter executions that use obfuscated environment variable expansion to construct and run PowerShell, matching a specific cmd /c or /r pattern containing a SET statement and encoded PowerShell invocation fragments. Such behavior matters because attackers often hide PowerShell payloads and reduce detection by dynamically building commands from environment variables. The detection relies on process creation telemetry, specifically the full CommandLine field for cmd.exe with the expected obfuscation characteristics.

Related detections9 linkedT1027 — drag to rearrange
Suspicious PowerShell Invoke-Expression with Replace Obfuscation
Malicious Emmenhtal JavaScript Loader Spawning Encoded PowerShell
Suspicious Python Interpreter Launching Encoded PowerShell via subprocess
Suspicious PS1Bot PowerShell Payload Written to ProgramData (via file_event)
Malicious Non-Interactive Encoded PowerShell Stager (via process_creation)
Suspicious Hidden PowerShell Executing Substring of Dropped File
PowerShell Encoded or Download-Cradle Command Line (via process_creation)
Obfuscated Encoded PowerShell Payload Deployed - PowerShell (via powershell)
Suspicious PowerShell AES Decryption and Reflective Method Invocation in SolarMarker
Windows Process Creation: Cmd Invokes PowerShell via Obfuscated Environment Variable Expansion
Pivot detection · T1027 · 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.