GhostTask

Ghost Scheduled Task

Inspired by WithSecure's research on Scheduled Task Tampering, they explained the feasibility of creating a scheduled task solely through registry key manipulation. Such an approach can bypass the generation of scheduled task creation event logs, such as 4698 and 106, providing a stealthier method for establishing persistence. In light of these insights, I developed this POC to demonstrate the creation of scheduled tasks through direct registry manipulation.

Creating a new scheduled task requires adding several registry keys and their associated values. Since the structure of the registry values related to scheduled tasks is undocumented, my methodology for constructing these structures primarily relied on trial and error, guided by comparisons with the registry values of legitimate scheduled tasks. Besides, I also referred to the interfaces in the Taskschd.h header file and drew extensively from Cyber.WTF Windows Registry Analysis – Today's Episode: Tasks. This research was invaluable in guiding me to formulate the structure of each registry value, such as Triggers, Actions, and DynamicInfo, which were essential to construct a functional scheduled task.

The tool offers the following features:

• Creates scheduled tasks with a restrictive security descriptor, making them invisible to all users.
• Establishes scheduled tasks directly via the registry, bypassing the generation of standard Windows event logs.
• Provides support to modify existing scheduled tasks without generating Windows event logs.
• Supports remote scheduled task creation (by using specially crafted Silver Ticket).
• Supports to run in C2 with in-memory PE execution module (e.g., BruteRatel's memexec)

*Remark:

• As of October 21, 2023, this tool has been tested on Windows 10, Windows Server 2016, 2019, and 2022
• As of October 21, 2023, no alert and no scheduled task creation event (ScheduledTaskCreated action type) will be generated in MDE (Microsoft Defender For Endpoint)
• To create a scheduled task using this tool, "NT AUTHORITY/SYSTEM" privileges are required
• After configuring the scheduled task, you'll need to either restart the system or await the next reboot for the task to be loaded into the "Schedule" service process and subsequently executed

Usage

…

Compile

x86_64-w64-mingw32-gcc GhostTask.c -o GhostTask.exe -lrpcrt4

Examples

1. Create a scheduled task that launches notepad.exe every Monday and Thursday at 2:12 pm:

GhostTask.exe localhost add demo "cmd.exe" "/c notepad.exe" LAB\Administrator weekly 14:12 monday,thursday

2. Modify existing scheduled task with new schedule type, user and program:

GhostTask.exe localhost add "Microsoft\Office\Office Automatic Updates 2.0" "cmd.exe" "/c notepad.exe" LAB\employee001 daily 20:37

3. Create a new scheduled task on remote computer:

As outlined in the WithSecure blog (Extra: Lateral Movement section), this technique can be used to remotely create a new scheduled task with a specially crafted Silver Ticket.

kerberos::golden /domain:LAB.CORP /sid:S-1-5-21-1111111111-1111111111-1111111111 /aes256:[aes256hash] /user:Administrator /service:cifs /target:dc01.lab.corp /sids:S-1-5-18 /endin:600 /renewmax:10080

Create a new scheduled task remotely on the DC01 server that launches notepad.exe every day at 3:19 PM:

GhostTask.exe DC01.lab.corp add demo "cmd.exe" "/c notepad.exe" LAB\Administrator daily 15:19

Credits

• WithSecure for their research WithSecure Scheduled Task Tampering
• Cyber.WTF for their research Windows Registry Analysis – Today’s Episode: Tasks
• ausecwa for his bof-registry