Windows Security Event 4698 Scheduled Task Creation for TeamCity UI

Flags Windows scheduled task creation events where the task name is TeamCity Settings UI and content contains a specific marker.

FreeReviewedSigma · Critical · v5
Product
windows
Service
security
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2023-10-24
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 matches Windows Security auditing events (EventID 4698) indicating a scheduled task was created with TaskName set to "\Windows TeamCity Settings User Interface" and specific task content containing the marker string "uTYNkfKxHiZrx3KJ". Attackers may create scheduled tasks to establish persistence or run exploitation-related actions under a controlled trigger. It relies on Security log telemetry that records scheduled task creation details, including TaskName and TaskContent.

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 Event 4698 Scheduled Task Creation for TeamCity UI
Pivot detection · T1053.005 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. 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.