Windows Network Connections Initiated by PowerShell (powershell.exe or pwsh.exe)

Flags outbound network connections initiated by PowerShell on Windows, excluding common local and private IP ranges.

FreeReviewedSigma · Low · v5
Product
windows
Category
network_connection
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2017-03-13
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 identifies network connections with Initiated set to true where the process image ends with powershell.exe or pwsh.exe. Such behavior is commonly used by malicious scripts to retrieve additional payloads or communicate with command and control over external IPs and uncommon network paths. It relies on Windows network connection telemetry that includes the initiating process image and destination IP, and it applies exclusions for local/private address ranges and specific IP CIDR ranges to reduce noise.

Related detections9 linkedT1059.001 — drag to rearrange
Malicious Script Host Spawning PowerShell in Gootloader Chain
Suspicious PsExec Service Launching Encoded PowerShell Payload
Suspicious PowerShell Remote Script Execution via IEX DownloadString
Malicious SharePoint ToolShell Post-Exploitation via Encoded PowerShell (via process_creation)
Suspicious In-Memory PowerShell Execution from Web Server via Automation Assembly (via image_load)
Malicious Qilin Chrome Credential Harvesting Script Execution via IPScanner (via process_creation)
Suspicious Hidden PowerShell Spawned by Script Host via process_creation
Suspicious Run Key Persistence Referencing PowerShell Script via registry_set
Malicious FIN7 Powertrash Loader Execution via Obfuscated PowerShell (via process_creation)
Windows Network Connections Initiated by PowerShell (powershell.exe or pwsh.exe)
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.