Suspicious Device Code Authentication via Microsoft Authentication Broker

PremiumReviewedSigma · High · v1
Product
azure
Service
signinlogs
Author
HuntRule
Published
2026-11-02
Updated
2026-11-02

ATT&CK techniques

Initial Access → Cred Access
  1. Recon

  2. Resource Dev

  3. Execution

  4. Discovery

  5. Lateral Movement

  6. Collection

  7. C2

  8. Exfiltration

  9. Impact

What it detects

This rule detects sign-ins using the Microsoft Authentication Broker application together with an Android device user-agent associated with token theft. This activity matches the Russian device-code phishing operation that spoofed European security events to trick targets into authorizing attacker-controlled devices. Successful abuse grants long-lived refresh tokens and lets the actor register rogue devices which enables persistent access to victim identities.

Related detections9 linkedT1078.004 — drag to rearrange
Suspicious Microsoft Entra Device Code Authentication Flow
Suspicious Salesforce Connected App OAuth Authorization from VPN Egress
Suspicious OAuth Device Code Sign-In to Authentication Broker via Tycoon 2FA
Suspicious OAuth Application Registration with Localhost Reply URL via Azure AD
Azure Audit Logs: Application URI Configuration Changes (AppAddress)
Suspicious Microsoft 365 OAuth Authorization to Visual Studio Code Client
Malicious AWS Cross-Account AssumeRole With Suspicious Session Names via CloudTrail (via aws)
Suspicious Okta SSO Access to Many Applications in Short Window
Suspicious M365 Password Spraying via Azure PowerShell AppId from Quad7 Botnet
Suspicious Device Code Authentication via Microsoft Authentication Broker
Pivot detection · T1078.004 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.