Windows: New Executables Named After System Processes in Non-System Paths

Alerts on creation of executables named like common system processes in unexpected Windows directories.

FreeReviewedSigma · Medium · v2
Product
windows
Category
file_event
Author
Sander Wiebing, Tim Shelton, Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2020-05-26
Updated
2026-07-31

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags file creation events where the created executable name matches a known system process (e.g., powershell.exe, svchost.exe, lsass.exe) but the target file is placed in directories outside standard Windows system locations. Naming system binaries in unexpected paths can help attackers blend into normal process naming and evade casual inspection. The detection relies on Windows file event telemetry capturing the created file path and executable filename, with exclusions for common internal Windows update/recovery and other allowed locations.

Related detections9 linkedT1036.005 — drag to rearrange
Scheduled Task Masquerading as Microsoft Wininet Config
Suspicious ALPHA SPIDER Rclone Exfiltration Tool Masquerading as System Binary (via process_creation)
Suspicious Axios NPM macOS Persistence Masquerading as Apple Service
Malicious Spoolsv Process Masquerading From Non-System Path (via process_creation)
Suspicious svchost.exe Execution From AppData Roaming Directory
Malicious StyleSmuggler (CVE-2026-75650) Post-Exploitation Implant Process (via process_creation)
Malicious WezRat Persistence via Chrome Updater Run Key
Malicious ValleyRAT RuntimeBroker Masquerade in RunTime Directory
Suspicious Execution of spools.exe from Public Directory
Windows: New Executables Named After System Processes in Non-System Paths
Pivot detection · T1036.005 · 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.