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 Python Execution via Renamed Synaptics Binary
MSBuild Executing Non-Project File or Remote Payload
Possible Ivanti Pulse Connect Secure Command Injection via License Keys-Status Endpoint (via webserver)
Possible Craft CMS RCE via Query-String CLI Option Injection
Possible Aspera Faspex Pre-Auth RCE via YAML Deserialization in package_relay (via webserver)
Possible Sitecore Pre-Auth RCE via Report.ashx Insecure Deserialization (via webserver)
Possible WatchGuard Pre-Auth RCE via agent login XML-RPC CVE-2022-26318
Possible Oracle Opera CGI Webshell Command Execution via operabin
Suspicious tar Extraction of Staged Archive to Temp (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.