Windows file creation of executable/script files in \Users\Public

Alerts on Windows file creation in \Users\Public\ with potentially malicious script/binary extensions.

FreeReviewedSigma · High · v2
Product
windows
Category
file_event
Author
The DFIR Report (SigmaHQ), DRL 1.1
Published
2025-01-23
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 the creation of files in the Windows public user directory (\Users\Public) with extensions commonly used for executable and script content (.bat, .dll, .exe, .hta, .js, .ps1, .vbe, .vbs). Placing such payloads in a widely accessible folder can support execution, staging, or lateral access by increasing discoverability and reach. It relies on file event telemetry that records the target filename during file creation.

Related detections9 linkedT1204 — drag to rearrange
Malicious Edge Abuse for Payload Download via Console (via process_creation)
Obfuscated Edge/Chrome Headless Feature Abuse for Payload Download (via process_creation)
Windows Process Creation: File Upload Clickfix Lure via Browser to Command Execution
Windows ClickFix/FileFix Clipboard Phishing Leading to Suspicious mshta/powershell Command Execution
Windows Process Creation: Explorer Command Lines with Unicode Whitespace Padding and '#'
Windows Registry RunMRU Path with Suspicious Space Characters and Delimiter
Windows Registry: Suspicious Space-Padded TypedPaths Details String
Windows Registry Set: FileFix-style Command Evidence in TypedPaths url1
Windows: Deno writes files from remote HTTPS content into AppData
Windows file creation of executable/script files in \Users\Public
Pivot detection · T1204 · 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.