Windows Security: Suspicious Scheduled Task Creation via Event 4698

Alerts on Windows scheduled task creation (EventID 4698) when TaskContent contains suspicious directories or command patterns.

FreeReviewedSigma · High · v2
Product
windows
Service
security
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 Security events (EventID 4698) where scheduled task content includes paths commonly used for staging or user-writable locations and command/script interpreter indicators. Attackers frequently use scheduled tasks for persistence and execution by embedding commands such as PowerShell, mshta, wscript/cscript, certutil, bitsadmin, wmic, or batch-like /c-/k arguments into the task payload. The detection relies on Security auditing data containing TaskContent fields with both path and command 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 Security: Suspicious Scheduled Task Creation via Event 4698
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.