Windows Scheduled Task Process Run from Suspicious File Locations

Alerts on Windows Task Scheduler process creation when the executed program runs from temp, downloads, desktop, or public-writable paths.

FreeReviewedSigma · Medium · v2
Product
windows
Service
taskscheduler
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-12-05
Updated
2026-07-31

ATT&CK techniques

Execution → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Defense Evasion

  5. Cred Access

  6. Discovery

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule flags Windows Scheduled Task process executions when the task’s program path contains common user-writable or temporary directories (for example, C:\Windows\Temp\, C:\Temp\, and user profile AppData\Local\Temp\). Attackers often abuse Task Scheduler to persistently execute malicious binaries or scripts from locations that are easier to stage or hide. It relies on Microsoft-Windows-TaskScheduler operational telemetry for the scheduled task process creation event (EventID 129) and matches the program path substrings.

Related detections9 linkedT1053.005 — drag to rearrange
Malicious CloudZ RAT Persistence via schtasks Running regasm.exe
Suspicious Scheduled Task Creation for WSPrint Persistence by UAT-9244
Malicious Scheduled Task Masquerading as GoogleUpdate Launching SSH Reverse Shell
Malicious Scheduled Task Creation TaskSystem via Interlock Ransomware
Malicious Scheduled Task Masquerading as Edge Update Running From Temp (via process_creation)
Suspicious Scheduled Task Created From XML Definition (via process_creation)
Malicious Scheduled Task Masquerade for Zardoor Persistence (via process_creation)
Malicious BugSleep Scheduled Task Persistence with Sample Comment
Suspicious Scheduled Task Masquerading As OneDrive (via process_creation)
Windows Scheduled Task Process Run from Suspicious File Locations
Pivot detection · T1053.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.