Windows PowerShell Invoke-WebRequest Download to Suspicious Paths

Alert when PowerShell uses Invoke-WebRequest/aliases with download flags and targets suspicious file locations.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-08-02
Updated
2026-07-30

ATT&CK techniques

C2
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. Exfiltration

  13. Impact

What it detects

This rule flags Windows process executions where a PowerShell-related binary (PowerShell ISE, PowerShell, or pwsh) runs a command that includes Invoke-WebRequest (or aliases like curl/wget/iwr) and output/download flags (-ur, -o). It also requires the command line to reference writing or directing content to commonly abused locations such as AppData, Desktop, Temp, Public, or paths under :\Windows. This behavior is significant because it can indicate scripted download-and-execute stages used to bring attacker-controlled payloads onto a host. It relies on process creation telemetry, including the image name and full command line.

Related detections9 linkedT1105 — drag to rearrange
Suspicious Remote Script Transfer via Bitsadmin (via process_creation)
Suspicious PowerShell Download Cradle via ClickFix Fake CAPTCHA (via process_creation)
Malicious Curl MSI Download to ProgramData via Process Creation
Suspicious CloudZ RAT Payload Download via curl to ProgramData
Suspicious Velociraptor Agent Deployment via msiexec From Cloud Storage
Suspicious PowerShell Download of lib.zip Archive
Suspicious File Download Via Bitsadmin Transfer
Suspicious PowerShell Download Of Text-Disguised Payload
Explorer WebDAV UNC Download Using At-Port Syntax
Windows PowerShell Invoke-WebRequest Download to Suspicious Paths
Pivot detection · T1105 · 9 related

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