Windows File Events: Known Offensive PowerShell Script File Creation

Alerts on creation of known offensive PowerShell/PowerShell module filenames on Windows.

FreeReviewedSigma · High · v2
Product
windows
Category
file_event
Author
Markus Neis, Nasreddine Bencherchali (Nextron Systems), Mustafa Kaan Demir, Georg Lauenstein (SigmaHQ), DRL 1.1
Published
2018-04-07
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 creation of Windows files whose names match a list of known offensive PowerShell scripts (e.g., exploitation, persistence, privilege escalation, credential theft tools) or contain “Invoke-Sharp” and end with .ps1. Attackers commonly drop these scripts to stage exploitation, execute payloads, or automate post-exploitation activity. The detection relies on file creation telemetry that includes the full target filename/path.

Reporting behind it

Related detections9 linkedT1059.001 — drag to rearrange
Suspicious Script Interpreter Spawned by Explorer via ClickFix Run Dialog (via process_creation)
Suspicious PowerShell Download Cradle via ClickFix Fake CAPTCHA (via process_creation)
Suspicious PowerShell EncodedCommand Spawned From Command Shell via Process Creation
Suspicious Script Download via Curl and PowerShell by Dohdoor
Malicious Mass Hyper-V Virtual Machine Shutdown via PowerShell by Kraken Ransomware
Suspicious PowerShell WebClient DownloadFile of Archive Payload (UAT-7237)
Suspicious SharePoint Worker Process Spawning Command Interpreter via ToolShell
Malicious Emmenhtal JavaScript Loader Spawning Encoded PowerShell
Suspicious Python Interpreter Launching Encoded PowerShell via subprocess
Windows File Events: Known Offensive PowerShell Script File Creation
Pivot detection · T1059.001 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. 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.