Systemd Timers

What the technique is

Adversaries may abuse systemd timers to perform task scheduling for initial or recurring execution of malicious code. Systemd timers are unit files with file extension.timer that control services. Timers can be set to run on a calendar event or after a time span relative to a starting point. They can be used as an alternative to Cron in Linux environments. Systemd timers may be activated remotely via the systemctl command line utility, which operates over SSH. Each.timer file must have a corresponding.service file with the same name, e.g., example.timer and example.service..service files are Systemd Service unit files that are managed by the systemd system and service manager. Privileged timers are written to /etc/systemd/system/ and /usr/lib/systemd/system while user level are written to ~/.config/systemd/user/. An adversary may use systemd timers to execute malicious code at system startup or on a scheduled basis for persistence. Timers installed using privileged paths may be used to maintain root level persistence. Adversaries may also install user level timers to achieve user level persistence.

What MITRE says you would watch

• AN0645

  Detects adversarial abuse of systemd timers by correlating file creation/modification of.timer and.service units in system directories with the execution of abnormal child processes launched by 'systemd' (PID 1), especially as root.