Suspicious D-Bus System Service Persistence File Creation

PremiumReviewedSigma · Medium · v1
Product
linux
Category
process_creation
Author
HuntRule
Published
2026-09-18
Updated
2026-09-18

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 writing of a D-Bus system service definition under the dbus-1 system-services directory, a persistence technique from the Elastic Linux persistence grand finale. A malicious service file causes D-Bus to launch attacker code on demand with elevated privileges. New service definitions created through shell tooling rather than package managers warrant review.

Related detections9 linkedT1543 — drag to rearrange
Suspicious GitHub Actions Runner In Hidden Directory via Shell (via process_creation)
Suspicious Self-Hosted GitHub Actions Runner Started As Root via Shell (via process_creation)
Suspicious GitHub Self-Hosted Runner Registration via Audit Log (via github)
Malicious Fire Ant Hypervisor Backdoor Artifacts on ESXi and vCenter (via file_event)
Malicious BRICKSTORM Backdoor Execution via Masqueraded Binary Path
Suspicious SonicWall SMA init.d Persistence Launching deploy_new.py
Malicious Linux XorDDoS gcc.pid Device Marker File via file_event
Windows Code Integrity: Blocked Driver Load Due to Revoked Certificate (Event ID 3023)
Windows PUA System Informer Driver Load via SystemInformer.sys
Suspicious D-Bus System Service Persistence File Creation
Pivot detection · T1543 · 9 related

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