Linux: Detect Modification of /etc/ld.so.preload for Shared Object Injection

Flags auditd activity where /etc/ld.so.preload is modified, indicating potential shared object injection.

FreeReviewedSigma · High · v3
Product
linux
Service
auditd
Author
E.M. Anhaus (originally from Atomic Blue Detections, Tony Lambert), oscd.community (SigmaHQ), DRL 1.1
Published
2019-10-24
Updated
2026-07-31

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 flags events where the file /etc/ld.so.preload is modified, indicating an attempt to influence dynamic library loading. Attackers can abuse this path to have arbitrary shared objects loaded into subsequently started processes, enabling code execution, persistence, and stealth. It relies on Linux auditd telemetry capturing file modification activity with type=PATH and name=/etc/ld.so.preload.

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 Shared Library Preload Persistence via ld.so.preload (via process_creation)
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
Pivot detection · T1574.006 · 8 related

Changelog

v3
  1. v3
    Candidate ingested via manual entry.2026-07-31
  2. v2
    Candidate ingested via manual entry.2026-07-31
  3. v1
    No changelog recorded for this version.2026-07-30

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