Suspicious Script Execution from Public User Folder Staging Directory

PremiumReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-07-09
Updated
2026-08-28

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 detects wscript, cscript, or PowerShell executing a .js or .ps1 file staged under C:\Users\Public, a staging location used in a Huntress-analyzed malspam-to-loader chain to hide script components. The Public folder is world-writable and rarely a legitimate home for scripts. Interpreter execution of scripts from this path is a strong indicator of loader staging activity.

Related detections9 linkedT1059.001 — drag to rearrange
Suspicious PowerShell Bypass Spawned by wscript Script Host
Suspicious RevengeHotels JS Loader Spawning PowerShell (via process_creation)
Windows AppLocker Audit-Mode Events Indicate Files Would Have Been Blocked
Windows AppLocker Blocked Application, Script, MSI, or Packaged-App Execution
Windows Process Creation: Suspicious Children Spawned by HTML Help (hh.exe)
Windows: Alert on Suspicious HH.EXE Process Execution
Suspicious Scheduled Task Running PowerShell Every Minute (via process_creation)
Malicious Script Host Spawning PowerShell With Invoke-Expression (via process_creation)
Possible React2Shell CVE-2025-55182 Prototype Pollution Exploitation
Suspicious Script Execution from Public User Folder Staging Directory
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.