Suspicious LD_PRELOAD Library Injection at Execution (via process_creation)

PremiumReviewedSigma · Medium · v1
Product
linux
Category
process_creation
Author
HuntRule
Published
2026-11-05
Updated
2026-11-05

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 a process launched with an inline LD_PRELOAD assignment that forces loading of a specified shared object. The Linux rootkits research shows this technique hooks library calls to hide activity and steal credentials. Because developers occasionally use LD_PRELOAD for debugging the rule is heuristic and should be reviewed against the target binary and library path.

Related detections9 linkedT1574.006 — drag to rearrange
Malicious ld.so.preload Overwrite for Privilege Escalation via PostgreSQL Escape (via file_event)
Suspicious Linux Dynamic Linker Hijacking via LD_PRELOAD or ld.so.preload (via process_creation)
Malicious ld.so.preload Hijack Loading libcext by Auto-Color (via process_creation)
Malicious ld.so.preload Persistence Modification on Ivanti Connect Secure (via file_event)
Suspicious Dynamic Linker Hijacking via ld.so.preload Modification
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)
Suspicious LD_PRELOAD Library Injection at Execution (via process_creation)
Pivot detection · T1574.006 · 9 related

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