Windows Process Creation: Detect Reversed PowerShell Command Tokens in CommandLine

Alerts on suspicious reversed token usage in PowerShell command lines on Windows, excluding -EncodedCommand / -enc.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Teymur Kheirkhabarov (idea), Vasiliy Burov (rule), oscd.community, Tim Shelton (SigmaHQ), DRL 1.1
Published
2020-10-11
Updated
2026-07-30

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 process creation events where PowerShell (powershell.exe or pwsh.exe) is launched with CommandLine content containing specific reversed-character tokens. Reversed strings are commonly used to obscure what the script is doing and may hinder straightforward command inspection. The detection relies on process creation telemetry and the Image and CommandLine fields, while excluding cases that include common encoded-command flags to reduce false positives.

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: Detect Reversed PowerShell Command Tokens in CommandLine
Pivot detection · T1027 · 9 related

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