Systemd Timers
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. Each .timer file must have a corresponding .service file with the same name. Privileged timers are written to /etc/systemd/system/ and /usr/lib/systemd/system while user level timers are written to ~/.config/systemd/user/. Adversaries may use systemd timers to execute malicious code at system startup or on a scheduled basis for persistence, and may leverage root-level timer paths to maintain privileged persistence.
let TimerPaths = dynamic([
"/etc/systemd/system/",
"/usr/lib/systemd/system/",
"/lib/systemd/system/",
".config/systemd/user/"
]);
let SuspiciousServiceContent = dynamic([
"/tmp/", "/dev/shm/", "/var/tmp/",
"bash -i", "nc ", "ncat ", "curl ", "wget ",
"python", "perl", "ruby",
"base64", "chmod +x", "chmod 777"
]);
// Detect systemctl commands enabling or starting timers
let SystemctlTimerEvents = Syslog
| where TimeGenerated > ago(24h)
| where ProcessName == "systemd" or SyslogMessage has "systemctl"
| where SyslogMessage has ".timer"
| where SyslogMessage has_any ("enable", "start", "daemon-reload", "link")
| extend TimerName = extract(@"([\w\-\.]+\.timer)", 1, SyslogMessage)
| extend Action = case(
SyslogMessage has "enable", "enabled",
SyslogMessage has "start", "started",
SyslogMessage has "daemon-reload", "daemon-reloaded",
"other")
| project TimeGenerated, Computer, ProcessName, SyslogMessage, TimerName, Action;
// Detect new .timer files written to systemd directories
let TimerFileCreation = DeviceFileEvents
| where TimeGenerated > ago(24h)
| where FileName endswith ".timer" or FileName endswith ".service"
| where FolderPath has_any (TimerPaths)
| extend IsPrivilegedPath = FolderPath has_any ("/etc/systemd/system/", "/usr/lib/systemd/system/", "/lib/systemd/system/")
| extend IsUserTimer = FolderPath has ".config/systemd/user/"
| project TimeGenerated, DeviceName, FileName, FolderPath, InitiatingProcessFileName,
InitiatingProcessCommandLine, InitiatingProcessAccountName,
IsPrivilegedPath, IsUserTimer;
union SystemctlTimerEvents, TimerFileCreation
| sort by TimeGenerated desc Data Sources
Required Tables
False Positives
- Legitimate software packages (e.g., apt, dnf, snap) installing systemd timers during package updates or installation
- System administrators creating scheduled maintenance timers (log rotation, backup jobs, certificate renewal via certbot)
- Configuration management tools (Ansible, Chef, Puppet, Salt) deploying timer units as part of infrastructure automation
- Cloud-init or provisioning scripts creating timers during VM initialization or boot
References (12)
- https://attack.mitre.org/techniques/T1053/006/
- https://wiki.archlinux.org/index.php/Systemd/Timers
- https://www.tecmint.com/control-systemd-services-on-remote-linux-server/
- https://www.bleepingcomputer.com/news/security/malware-found-in-arch-linux-aur-package-repository/
- https://gist.github.com/campuscodi/74d0d2e35d8fd9499c76333ce027345a
- https://lists.archlinux.org/pipermail/aur-general/2018-July/034153.html
- https://www.hybrid-analysis.com/sample/28553b3a9d2ad4361d33d29ac4bf771d008e0073cec01b5561c6348a608f8dd7?environmentId=300
- http://man7.org/linux/man-pages/man1/systemd.1.html
- https://www.freedesktop.org/software/systemd/man/systemd.timer.html
- https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1053.006/T1053.006.md
- https://github.com/SigmaHQ/sigma/tree/master/rules/linux
- https://pberba.github.io/security/2022/01/30/linux-threat-hunting-for-persistence-systemd-timers-and-cron/
Unlock Pro Content
Get the full detection package for T1053.006 including response playbook, investigation guide, and atomic red team tests.