Windows DLL Load Indicates Potential Azure Browser SSO OAuth Token Request Abuse

Alerts on MicrosoftAccountTokenProvider.dll loads on Windows, with process-based exclusions, as a signal for potential Azure Browser SSO token activity.

FreeReviewedSigma · Low · v2
Product
windows
Category
image_load
Author
Den Iuzvyk (SigmaHQ), DRL 1.1
Published
2020-07-15
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 identifies cases where MicrosoftAccountTokenProvider.dll is loaded, excluding common benign BackgroundTaskHost.exe and developer/browser host processes. Such a DLL load can be consistent with browser SSO behavior that requests OAuth 2.0 refresh tokens for Azure AD–authenticated users, which an attacker could abuse to authenticate in a browser as that user. The detection relies on Windows image-load telemetry capturing the DLL path, along with process path conditions to reduce straightforward false positives.

Related detections9 linkedT1574.001 — drag to rearrange
Suspicious Service DLL Hijack of IKEEXT or PrintNotify
Malicious PowerShell Spawned by Masqueraded NVIDIA GeForce Experience Binary
Suspicious msimg32.dll Loaded from Non-System Directory
DLL Side-Loading via Signed Binary Loading Known Malicious Helper DLL
Suspicious DLL Sideloading via msdtc oci.dll Install (via process_creation)
Suspicious wmicodegen.dll Sideload by inetinfo.exe (UAT-8099 Cobalt Strike)
Suspicious LucidRook DismCore.dll Side-Load into Browser Process
Suspicious Encrypted Implant File Creation for DLL Search Order Hijacking (RainyDay Turian PlugX)
Suspicious RoboForm Signed Binary Executed From Non-Standard Path (via process_creation)
Windows DLL Load Indicates Potential Azure Browser SSO OAuth Token Request Abuse
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.