Windows schtasks.exe scheduled task creation from suspicious folders

Alerts on schtasks.exe /create using PowerShell/cmd and suspicious folder paths like ProgramData.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-04-15
Updated
2026-07-30

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 process creation where schtasks.exe is used with a /create command and the action references suspicious folder paths such as C:\ProgramData\ or %ProgramData%. Attackers often use scheduled tasks for persistence by placing commands in commonly abused locations and invoking them via command-line tooling. It relies on Windows process creation telemetry, matching schtasks.exe invocations and the presence of /create along with PowerShell/cmd command patterns and suspicious folder strings within the CommandLine.

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 schtasks.exe scheduled task creation from suspicious folders
Pivot detection · T1053.005 · 9 related

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