Suspicious Systemd Service Unit Creation In System Directory

PremiumReviewedSigma · Medium · v1
Product
linux
Category
file_event
Author
HuntRule
Published
2026-09-16
Updated
2026-09-16

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 detects creation or modification of a systemd service unit file under the system unit directories which is a common Linux persistence mechanism where an ExecStart directive is pointed at a reverse shell or malicious payload. Adversaries install rogue systemd units so their code runs automatically at boot with elevated privileges.

Related detections9 linkedT1543.002 — drag to rearrange
Malicious Systemd Service Persistence via ExecStartPost Hidden Path on Linux
Malicious Koske Persistence via Systemd Service and Shell Profile Hijack (via process_creation)
Suspicious Linux CoinMiner Watchdog Staging in Shared Memory (via process_creation)
Suspicious systemd Service Persistence Creation (via process_creation)
Masquerading Systemd Service Masquerade via Systemctl Reenable of rsyslogd (via process_creation)
Suspicious Systemd Service Masquerading as Sysmon (via file_event)
APT28 httd Implant Persistence via systemd linux.service from Boot Directory (via process_creation)
Malicious Keyhunter Worker Systemd Unit File Creation
Masquerading Execution of Binary from Var Log Directory (via process_creation)
Suspicious Systemd Service Unit Creation In System Directory
Pivot detection · T1543.002 · 9 related

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