| ID | Name |
|---|---|
| T1053.002 | At |
| T1053.003 | Cron |
| T1053.005 | Scheduled Task |
| T1053.006 | Systemd Timers |
| T1053.007 | Container Orchestration Job |
Adversaries may abuse the cron utility to perform task scheduling for initial or recurring execution of malicious code.[1] The cron utility is a time-based job scheduler for Unix-like operating systems. The crontab file contains the schedule of cron entries to be run and the specified times for execution. Any crontab files are stored in operating system-specific file paths.
An adversary may use cron in Linux or Unix environments to execute programs at system startup or on a scheduled basis for Persistence. In ESXi environments, cron jobs must be created directly via the crontab file (e.g., /var/spool/cron/crontabs/root).[2]
| ID | Name | Description |
|---|---|---|
| S0504 | Anchor | |
| G0082 | APT38 |
APT38 has used cron to create pre-scheduled and periodic background jobs on a Linux system.[4] |
| G1023 | APT5 |
APT5 has made modifications to the crontab file including in |
| S0401 | Exaramel for Linux |
Exaramel for Linux uses crontab for persistence if it does not have root privileges.[6][7] |
| S0588 | GoldMax |
The GoldMax Linux variant has used a crontab entry with a |
| S1198 | Gomir |
Gomir will configure a crontab for process execution to start the backdoor on reboot if it is not initially running under group 0 privileges.[9] |
| S0163 | Janicab | |
| S0599 | Kinsing |
Kinsing has used crontab to download and run shell scripts every minute to ensure persistence.[11] |
| S0198 | NETWIRE | |
| S1107 | NKAbuse |
NKAbuse uses a Cron job to establish persistence when infecting Linux hosts.[13] |
| C0048 | Operation MidnightEclipse |
During Operation MidnightEclipse, threat actors configured cron jobs to retrieve payloads from actor-controlled infrastructure.[14][15] |
| S0587 | Penquin |
Penquin can use Cron to create periodic and pre-scheduled background jobs.[16] |
| G0106 | Rocke |
Rocke installed a cron job that downloaded and executed files from the C2.[17][18][19] |
| S0468 | Skidmap | |
| S0374 | SpeakUp | |
| S0341 | Xbash |
Xbash can create a cronjob for persistence if it determines it is on a Linux system.[22] |
| ID | Mitigation | Description |
|---|---|---|
| M1047 | Audit |
Review changes to the |
| M1018 | User Account Management |
|
| ID | Name | Analytic ID | Analytic Description |
|---|---|---|---|
| DET0290 | Cross-Platform Detection of Cron Job Abuse for Persistence and Execution | AN0805 |
Detects creation or modification of crontab entries by non-root users or from abnormal parent processes, followed by the execution of uncommon binaries at scheduled intervals. |
| AN0806 |
Detects crontab job additions or modifications via |
||
| AN0807 |
Detects direct modification of crontab entries in /var/spool/cron/crontabs/root or /etc/rc.local.d/local.sh followed by execution of scripts linked to lateral movement or malware persistence. |