Windows Schtasks.exe renamed execution used to create, modify, run, or delete scheduled tasks

Alerts on scheduled task management commands that use a renamed schtasks.exe binary on Windows.

FreeReviewedSigma · High · v3
Product
windows
Category
process_creation
Author
Swachchhanda Shrawan Poudel (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2025-11-27
Updated
2026-10-03

ATT&CK techniques

Execution → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Cred Access

  5. Discovery

  6. Lateral Movement

  7. Collection

  8. C2

  9. Exfiltration

  10. Impact

What it detects

This rule flags process creation events where the executed image ends with \schtasks.exe or the process original file name is schtasks.exe, while the command line includes schtasks-related operations such as /create, /delete, /query, /change, /run, or /end. Renaming schtasks.exe can help attackers blend into expected tooling while using it for persistence via scheduled tasks. The detection relies on Windows process creation telemetry, including Image, OriginalFileName, and CommandLine, and excludes cases involving openfiles queries.

Related detections9 linkedT1053.005 — drag to rearrange
Suspicious Scheduled Task CacheTask Reconfigured to Run as SYSTEM
Malicious NodeSnake RAT Persistence via Scheduled Task and Node.js (via process_creation)
Malicious Scheduled Task Masquerading as Windows Defender Sync via schtasks (via process_creation)
Suspicious Scheduled Task Creation Launching mshta via schtasks (via process_creation)
Suspicious Renamed PowerShell Binary Execution (via process_creation)
Suspicious Service or Task Named windowsinspectionupdate (via process_creation)
Possible DarkGate Process Injection via iTunesHelper Spawning vbc.exe
Suspicious Renamed PowerShell Copied from System32 via Batch Loader
Suspicious Scheduled Task Creation Referencing dllFake Batch Scripts (via process_creation)
Windows Schtasks.exe renamed execution used to create, modify, run, or delete scheduled tasks
Pivot detection · T1053.005 · 9 related

Changelog

v3
  1. v3
    Candidate ingested via manual entry.2026-10-03
  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.