Suspicious OAuth Device Code Sign-In to Authentication Broker via Tycoon 2FA

PremiumReviewedSigma · High · v1
Product
azure
Service
signinlogs
Author
HuntRule
Published
2026-09-20
Updated
2026-09-20

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 a successful device code authentication against the Microsoft Authentication Broker application. Tycoon 2FA operators adopted OAuth device code phishing to trick users into authorizing attacker-controlled sessions and mint long-lived tokens for non-interactive Exchange and Graph access. Device code grants to the broker app are rare in normal use and indicate token theft.

Related detections9 linkedT1078.004 — drag to rearrange
Suspicious Device Code Authentication via Microsoft Authentication Broker
Suspicious Microsoft Entra Device Code Authentication Flow
Suspicious Salesforce Connected App OAuth Authorization from VPN Egress
Suspicious OfficeHome Sign-In With Axios User Agent via Tycoon 2FA Proxy
Suspicious AiTM Session Cookie Exfiltration to log_cookie Endpoint
Suspicious Entra Sign-In to OfficeHome with axios User Agent
Suspicious OAuth Application Registration with Localhost Reply URL via Azure AD
Azure Audit Logs: Application URI Configuration Changes (AppAddress)
Malicious Context.ai OAuth Application Authorization by Client ID (via google_workspace)
Suspicious OAuth Device Code Sign-In to Authentication Broker via Tycoon 2FA
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.