The feature runs a program or script at a set time or on a repeat. Attackers use it to start malicious code, to keep their access after a restart, or to run code with higher privileges.
How it works
All major operating systems include tools that run programs or scripts at a chosen date and time. Attackers abuse these tools to start malicious code once or to run it again and again.
A scheduled task can run at system startup or on a fixed schedule, which helps an attacker keep access. It can also run under a chosen account, including one with higher privileges. A task can also be set up on another system, but this usually requires membership in an admin or otherwise privileged group there.
Because the scheduler is a trusted system component, a one-time run can look like normal system activity. On Windows, the Scheduled Task sub-technique (T1053.005) also covers hidden tasks that may not show up in the tools defenders use to list tasks. MITRE lists five sub-techniques: T1053.002 At, T1053.003 Cron, T1053.005 Scheduled Task, T1053.006 Systemd Timers and T1053.007 Container Orchestration Job.
A real example
- MITRE ATT&CK lists Lokibot as having a second stage DLL that sets a timer to schedule its next run.
- MITRE ATT&CK lists a campaign MITRE names 2025 Poland Wiper Attacks as setting scheduled tasks on a network security device to run attacker-made command line scripts every week.
- Recorded Future says HOOKEDGE's 30-minute scheduled task starts the first stage of the backdoor.
Who uses it
- Ransomware group Qilin Qilin, also tracked as Agenda, is a ransomware as a service family that MITRE ATT&CK says has been active since at least 2022. Active · Since 2022 · Ransomware as a service
- Ransomware group The Gentlemen Ransomware Group The Gentlemen is a ransomware-as-a-service operation. Active · Since 2025 · Ransomware as a service with double extortion; affiliates keep 90% of each ransom (per Unit 42, Sophos and Check Point)
Seen in incidents
- Incident AOMEI Backupper installer supply chain compromise Between April and July 2026, attackers briefly tampered with the update files of the AOMEI Backupper installer, so that the backup program fetched and ran a backdoor. April to July 2026 · Telecommunications
- Incident Poland energy sector attacks On 29 December 2025, coordinated destructive attacks hit more than 30 wind and solar farms, a large combined heat and power plant and a manufacturing company in Poland. December 2025 · Energy and utilities
How to detect
-
Watch for new or changed tasks
Log the creation, change and deletion of scheduled tasks, whether made through the scheduler, management interfaces or scripts.
-
Link the task to what runs next
Look for a task change followed by an unusual process starting from it, especially a task created under a SYSTEM or otherwise suspicious account.
-
Look for hidden or odd tasks
Compare the tasks you can list with expected ones. Tasks that are hidden, or that run at unusual intervals or as unusual users, deserve a closer look.
-
Data sources MITRE lists
Command Execution, File Creation, File Modification, Process Creation, Scheduled Job Creation
How to defend
-
Limit who can schedule tasks
Let only authorized administrators create scheduled tasks on remote systems, and remove paths that let ordinary accounts gain more privileges.
-
Run tasks as the signed-in account
Configure scheduling settings so tasks run under the authenticated account instead of SYSTEM, and let only the Administrators group raise scheduling priority.
-
Restrict file and directory permissions
Set permissions that are not open to every user, so that tasks and the files they run cannot easily be altered.
-
Audit for permission weaknesses
Check systems for weak permissions on scheduled tasks that could be used to gain higher privileges.
Frequently Asked Questions
What is Scheduled Task/Job (T1053)?
Scheduled Task/Job is a technique where an attacker uses the task scheduling feature built into an operating system. The feature runs a program or script at a set time or on a repeat, and attackers use it to run malicious code, keep access after a restart or gain higher privileges.
Why do attackers abuse task scheduling?
All major operating systems include tools that run programs at a chosen time. A task can run at startup or on a schedule, which helps an attacker keep access, and it can run under a chosen account, including a privileged one. Because the scheduler is trusted, activity can look normal.
How can defenders detect malicious scheduled tasks?
Log the creation, change and deletion of scheduled tasks, however they were made. Look for a task change followed by an unusual process starting from it, especially a task created under a SYSTEM or otherwise suspicious account. Compare listed tasks with expected ones to find hidden or odd tasks.
How do I defend against Scheduled Task/Job abuse?
Let only authorized administrators create scheduled tasks on remote systems, and set tasks to run under the signed-in account instead of SYSTEM. Use restrictive file and directory permissions, and audit systems for weak permissions on scheduled tasks that could give higher privileges.
