Windows Registry: New TaskCache entry created by unusual process image

Alerts when TaskCache registry entries are created by processes other than a defined set of expected Windows binaries.

FreeReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
Syed Hasan (@syedhasan009) (SigmaHQ), DRL 1.1
Published
2021-06-18
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 registry writes that create a new entry under the TaskCache path in Schedule. It is suspicious because attackers can tamper with or establish scheduled task-related cache artifacts to persist or execute malicious activity. Detection relies on registry set telemetry matching the TargetObject under TaskCache while excluding changes made by several known Windows and common application processes.

Related detections9 linkedT1053.005 — drag to rearrange
Windows Process Creation: Scheduled Task Creation via schtasks and wscript/vbscript
Suspicious Scheduled Task Creation Running VBS at One Minute Interval via Blind Eagle (via process_creation)
Suspicious Latrodectus Payload Execution from Custom_update Directory (via process_creation)
Suspicious Scheduled Task Persistence Named SchedulerLsass via schtasks (via process_creation)
Malicious SYSTEM Persistence via Scheduled Task Running rundll32 at Startup (via process_creation)
Suspicious Per-Minute SYSTEM Scheduled Task With Highest Privileges
Suspicious Scheduled Task Executing Rundll32 DLL Export by Ordinal
Suspicious Scheduled Task CacheTask Reconfigured to Run as SYSTEM
Malicious NodeSnake RAT Persistence via Scheduled Task and Node.js (via process_creation)
Windows Registry: New TaskCache entry created by unusual process image
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.