huntrule

Windows PowerShell execution from C:\Users\Public

Flags PowerShell command lines that reference C:\Users\Public, indicating likely script execution from a common public staging area.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Max Altgelt (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-04-06
Updated
2026-07-30
AnalysisDetection

ATT&CK techniques

Execution

  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. C2

  13. Exfiltration

  14. Impact

What it detects

This rule identifies process creation where PowerShell (powershell.exe or pwsh.exe) is invoked with arguments pointing to scripts or content located in C:\Users\Public. Attackers may use this common writable public directory to stage files and then execute them to run code with the user’s context. The detection relies on Windows process creation telemetry, matching the PowerShell binary name and specific command-line substrings referencing C:\Users\Public and related flags.

Reporting behind it

Related detections9 linkedT1059.001 — drag to rearrange
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)
Suspicious XOR Obfuscated PowerShell from ClickFix Distribution
Suspicious Hidden PowerShell Web Download via ClickFix Tactic
Malicious MS-SQL Server Spawning Command Shell via Mallox
Windows PowerShell execution from C:\Users\Public
Pivot detection · T1059.001 · 9 related

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