Windows Security Mitigations: Unsigned DLL Blocked from User-Writable Paths

Alerts on blocked unsigned DLL loads targeting public, downloads, desktop, or temp directories in Windows Security Mitigations logs.

FreeReviewedSigma · High · v2
Product
windows
Service
security-mitigations
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-08-03
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 security-mitigations events where processes are blocked from loading unsigned DLLs located in common suspicious, user-writable locations (e.g., Users\Public, PerfLogs, Desktop, Downloads, and local Temp directories). Attackers often place unsigned components in these paths to execute or persist code while evading signature validation. Detection relies on Windows Security Mitigations telemetry (EventID 11 and 12) that records the blocked DLL load attempts and the associated image path.

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 Security Mitigations: Unsigned DLL Blocked from User-Writable Paths
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.