Suspicious Linux Boot Persistence via rc.local or init.d Modification (via file_event)

PremiumReviewedSigma · Medium · v1
Product
linux
Category
file_event
Author
HuntRule
Published
2026-10-06
Updated
2026-10-06

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 modification of /etc/rc.d/rc.local or files under /etc/init.d which the DinodasRAT Linux implant abuses to survive reboots by registering itself as a boot-time service which is a common Linux persistence technique warranting review.

Related detections9 linkedT1543.002 — drag to rearrange
Suspicious Fake vSphere Service Installation with SELinux Disable via Command Line (via process_creation)
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
Malicious systemd-daemon Masquerading Binary Execution on Linux
Suspicious Masquerading systemd Unit display-managerd Creation via File System
Suspicious Linux Boot Persistence via rc.local or init.d Modification (via file_event)
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.