Linux auditd: systemd service file creation under systemd directories

Identifies new systemd unit file creation events under common systemd directories using auditd PATH create logs.

FreeReviewedSigma · Medium · v3
Product
linux
Service
auditd
Author
Pawel Mazur (SigmaHQ), DRL 1.1
Published
2022-02-03
Updated
2026-07-31

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags file creation events for systemd service units under standard systemd locations (e.g., /usr/lib/systemd/system/ and /etc/systemd/system/) and user unit paths containing /.config/systemd/user/. Adversaries can abuse these locations to persist by having systemd start attacker-controlled code via newly created unit files. It relies on Linux auditd PATH create telemetry that includes the created file path.

Related detections9 linkedT1543.002 — drag to rearrange
Malicious Keyhunter Worker Persistence via Systemd Service
Malicious Systemd Service Masquerading as Sd-Pam Helper
Malicious Linux systemd Persistence nvmconf.service
Suspicious Linux Persistence via sed Edit of Boot and Init Files
Suspicious systemd Service Persistence via GRIDTIDE xapt
Suspicious Python Execution of Fake Sysmon Script From Config Directory
Suspicious Linux Boot Persistence via rc.local or init.d Modification (via file_event)
Malicious systemd-daemon Masquerading Binary Execution on Linux
Suspicious Masquerading systemd Unit display-managerd Creation via File System
Linux auditd: systemd service file creation under systemd directories
Pivot detection · T1543.002 · 9 related

Changelog

v3
  1. v3
    Candidate ingested via manual entry.2026-07-31
  2. v2
    Candidate ingested via manual entry.2026-07-31
  3. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.