Windows Image Load of Specific System DLLs Not Normally Present in System Directories

Alerts on image load events for specific system-path DLLs with unexpected “phantom” DLL names on Windows.

FreeReviewedSigma · High · v2
Product
windows
Category
image_load
Author
Nasreddine Bencherchali (Nextron Systems), SBousseaden (SigmaHQ), DRL 1.1
Published
2022-12-09
Updated
2026-07-31

ATT&CK techniques

Execution → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags process image loads for a set of specific system DLL paths that are typically not present on the host (or at least not in system directories) but may still be requested by legitimate processes. Such unexpected DLL loads can indicate phantom DLL hijacking, where attackers aim to have a process load a malicious library using a system-matching name and location. It relies on Windows image load telemetry that includes the loaded module path, along with signature-related fields to filter out Microsoft-signed, valid signatures.

Related detections9 linkedT1574.001 — drag to rearrange
Malicious DLL Sideloading via consent.exe Loading msimg32.dll (via image_load)
Malicious Bumblebee DLL Sideload of msimg32 by consent from Non-System Path (via image_load)
Suspicious BugSplat Binary Sideloading bugsplatrc.dll via DLL Search Order Hijack
Suspicious SentinelOne Binary Sideloading sentinelagentcore.dll
Suspicious 7-Zip Executable Sideloading 7z.dll Loader
Suspicious Loading of Masqueraded EndpointDlp.dll Backdoor
Suspicious Trend Micro Binary Sideloading tmdglog.dll
Suspicious DLL Sideloading via ProtonVPN Executable (via image_load)
Suspicious DLL Sideloading via OneDriveStandaloneUpdater (via image_load)
Windows Image Load of Specific System DLLs Not Normally Present in System Directories
Pivot detection · T1574.001 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. 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.