Windows Schtasks.exe Scheduled Task Creation or Modification with Suspicious Schedule Types

Alerts on schtasks.exe commands that schedule tasks using ONLOGON/ONSTART/ONCE/ONIDLE with potentially malicious privilege context.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-09-09
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 executions of schtasks.exe where the command line includes specific schedule trigger types such as ONLOGON, ONSTART, ONCE, or ONIDLE. Attackers use scheduled tasks to persist and execute code at chosen events, making trigger selection an important signal. The detection relies on Windows process creation telemetry and matches on schtasks.exe plus trigger strings in the command line, while excluding cases that contain certain privilege indicators.

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 or Modification with Suspicious Schedule Types
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.