Malicious Shared Library Preload Persistence via ld.so.preload (via process_creation)

PremiumReviewedSigma · High · v1
Product
linux
Category
process_creation
Author
HuntRule
Published
2026-09-03
Updated
2026-09-03

ATT&CK techniques

Execution → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Cred Access

  5. Discovery

  6. Lateral Movement

  7. Collection

  8. C2

  9. Exfiltration

  10. Impact

What it detects

This rule detects modification of /etc/ld.so.preload, which forces a shared library to load into every dynamically linked process, a stealthy persistence and privilege-escalation technique used by Linux rootkits. Ld.so.preload hijacking is tracked in the Red Canary Threat Detection Report. Detecting the change surfaces a system-wide library hijack.

Related detections8 linkedT1574.006 — drag to rearrange
Malicious Koske Userland Rootkit Installation via ld.so.preload (via file_event)
Malicious TeamTNT prochider Rootkit Deployment as Shared Object (via file_event)
Malicious perfctl Rootkit Library Drop via ld.so.preload (via file_event)
Malicious Userland Rootkit Persistence via ld.so.preload on Linux
Suspicious Bootkitty Rootkit Component Drop under opt via File System
Malicious LD_PRELOAD Rootkit Persistence via ld.so.preload
Linux Code Injection via ld.so Preload File (/etc/ld.so.preload)
Linux: Detect Modification of /etc/ld.so.preload for Shared Object Injection
Malicious Shared Library Preload Persistence via ld.so.preload (via process_creation)
Pivot detection · T1574.006 · 8 related

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