Registry keys:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\Taskcache\Tasks\<TASK_GUID>
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Schedule\Taskcache\Tree\<TASK_NAME>
Overview
Scheduled tasks are used to automatically perform a task on the system whenever the criteria associated with the scheduled task are met. Scheduled tasks can be run at a defined time, repeatedly at set intervals, or when a specific event occurs, such as the system boot.
The following registry keys are created upon the creation of a new scheduled task:
Schedule\Taskcache\Tasks\<TASK_GUID>.Schedule\Taskcache\Tree\<TASK_NAME>.
A scheduled task can be created through direct manipulation of the
registry only, as implemented in
GhostTask for instance. Creating a
scheduled task this way will not generate task creation ETW events.
However, the task will not be functional until the Schedule service is
restarted or the task configuration is modified, to trigger a reload by the
Schedule service. Modifying the task would generate associated ETW events
(channel Microsoft-Windows-TaskScheduler/Operational, event 140, or channel
Security, non-default event 4702).
Additionally, a scheduled task can continue to run even if its associated
elements in the registry and/or on disk (XML files) are deleted. The
scheduled task will be fully hidden but will persist until the system is
rebooted or the svchost.exe process associated with that task is terminated.
However, the ETW events related to the task execution will still be
generated.
Information of interest
Each scheduled task configuration is defined in a dedicated subkey under
Schedule\Taskcache\Tasks, identified by the task GUID (i.e.
Schedule\Taskcache\Tasks\<TASK_GUID>).
For each task, the following notable information is available under the task
GUID root key Schedule\Taskcache\Tasks\<TASK_GUID>:
-
The task path.
-
Some lifecycle timestamps of the task: created on, last start, and last stop in the
DynamicInfovalue (in binary format). -
The task trigger(s) (
Triggersvalue) and action(s) (Actionsvalue) in binary, non-human-readable format. A single scheduled task can be associated with one or multiple trigger(s) and one or multiple action(s). A single task can thus execute multiple distinct executables. -
The task security descriptor (in
SDDLnotation), in theSecurityDescriptorvalue.
The mapping between a task name and its GUID can be done using the subkeys of
the Schedule\Taskcache\Tree keys. Indeed, each task is referenced by its name
as a subkey of the Schedule\Taskcache\Tree key (i.e.
Schedule\Taskcache\Tree\<TASK_NAME>), with the GUID of the task
stored in the Id value.
Additionally, the Schedule\Taskcache\Tree\<TASK_NAME> key holds the
Security Descriptor of the scheduled task (in the SD value). Removing this
value will hide the scheduled task from utilities such as schtasks or the
Task Scheduler, while leaving it functional. This was implemented in the
Tarrask malware, as discovered by Microsoft.
References
-
Microsoft - Tarrask malware uses scheduled tasks for defense evasion
-
cyber.wtf - Luca Ebach - Windows Registry Analysis - Today’s Episode: Tasks
View on GitHub