Windows PowerShell Script Execution via Redirected Input Stream

Flags PowerShell/pwsh executions where the command line includes redirected input ("- <").

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Moriarty Meng (idea), Anton Kutepov (rule), oscd.community (SigmaHQ), DRL 1.1
Published
2020-10-17
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 identifies PowerShell or pwsh being launched with a command line containing a redirected input indicator ("- <"). Attackers can use redirected input to pass script content or commands through the process invocation, helping execution blend into less obvious command-line patterns. Detection relies on Windows process creation telemetry capturing the PowerShell executable path and the full command line.

Related detections9 linkedT1059 — drag to rearrange
AutoIt Script Execution via A3X Payload
Suspicious Python Execution via Renamed Synaptics Binary
MSBuild Executing Non-Project File or Remote Payload
Possible Ivanti Pulse Connect Secure Command Injection via License Keys-Status Endpoint (via webserver)
Possible Craft CMS RCE via Query-String CLI Option Injection
Possible Aspera Faspex Pre-Auth RCE via YAML Deserialization in package_relay (via webserver)
Possible Sitecore Pre-Auth RCE via Report.ashx Insecure Deserialization (via webserver)
Possible WatchGuard Pre-Auth RCE via agent login XML-RPC CVE-2022-26318
Possible Oracle Opera CGI Webshell Command Execution via operabin
Windows PowerShell Script Execution via Redirected Input Stream
Pivot detection · T1059 · 9 related

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