Windows DLL Sideloading via Abusable DLLs Loaded from Suspicious Locations

Flags Windows module loads of specific abusable DLL names from public, temp, or user folders consistent with potential DLL sideloading.

FreeReviewedSigma · High · v2
Product
windows
Category
image_load
Author
X__Junior (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2023-07-11
Updated
2026-07-31

ATT&CK techniques

Execution
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags Windows image loads of specific abusable DLLs when they are loaded from paths commonly associated with user-writable or transient locations. Attackers may leverage DLL search order or side-loading to execute attacker-controlled code under a legitimate process. The detection relies on image_load telemetry that records the loaded module path, matching both the DLL name suffixes and suspicious directory substrings.

Related detections9 linkedT1059 — drag to rearrange
Suspicious OneNote Spawning Command or Script Interpreter via Spear-Phishing (via process_creation)
Malicious Web Server Process Spawning Command Interpreter via Web Shell (via process_creation)
Suspicious VMware Guest Operation Output Staging in vmware-system Temp Directory (via file_event)
Malicious Command Shell Spawned by SQL Server via Process Creation (via process_creation)
Suspicious Script Interpreter Spawned by Excel via DarkGate Lure
Suspicious AutoHotkey Script Execution from User Writable Path by DarkGate
Malicious China Chopper Web Shell Command Pattern in IIS Worker Process (via process_creation)
Malicious AutoHotKey Runner AutoNotify Executing AHKBot Looper Script (via process_creation)
Malicious IIS Worker Process Spawning Command Shell after ASP.NET ViewState Injection (via process_creation)
Windows DLL Sideloading via Abusable DLLs Loaded from Suspicious Locations
Pivot detection · T1059 · 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.