Suspicious Linux Persistence via sed Edit of Boot and Init Files

PremiumReviewedSigma · Medium · v1
Product
linux
Category
process_creation
Author
HuntRule
Published
2026-10-12
Updated
2026-10-12

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 sed performing an in-place edit of Linux boot and service files such as rc.local, init.d scripts and systemd units, matching BRICKSTORM persistence that injects the Go backdoor into system startup. Modifying these startup mechanisms ensures the espionage implant relaunches after reboot.

Related detections9 linkedT1543.002 — drag to rearrange
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
Suspicious Systemd Service Unit Written to System Directory (via process_creation)
Suspicious Systemd Service Unit Creation In System Directory
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 Persistence via sed Edit of Boot and Init Files
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.