PowerShell Classic bXOR Operator Usage in Command Line

Identifies PowerShell classic executions from ConsoleHost using the -bxor operator in the command line.

FreeReviewedSigma · Low · v5
Product
windows
Category
ps_classic_start
Author
Teymur Kheirkhabarov, Harish Segar (SigmaHQ), DRL 1.1
Published
2020-06-29
Updated
2026-07-31

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 PowerShell Classic command lines executed via ConsoleHost that include the substring " -bxor ", indicating use of the bitwise XOR operator. Attackers may use XOR to obfuscate or transform payloads to reduce the visibility of malicious content. It relies on Windows PowerShell Classic process start telemetry with access to the full CommandLine value and the HostName field to confirm the execution context.

Related detections9 linkedT1059.001 — drag to rearrange
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
Suspicious Script Interpreter Spawned by Explorer via ClickFix Run Dialog (via process_creation)
Suspicious PowerShell Download Cradle via ClickFix Fake CAPTCHA (via process_creation)
PowerShell Classic bXOR Operator Usage in Command Line
Pivot detection · T1059.001 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. 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.