Windows Schtasks Execution with Renamed schtasks.exe Binary

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

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

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 where schtasks functionality is invoked via command-line parameters commonly used for creating, modifying, deleting, querying, running, or ending scheduled tasks, but the executed binary name does not match the expected schtasks.exe path. Attackers often rename legitimate binaries to reduce the likelihood of security tooling detecting task scheduling activity. The detection relies on Windows process creation telemetry, including the process Image/OriginalFileName and the CommandLine containing schtasks-related flags and operations.

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 Execution with Renamed schtasks.exe Binary
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.