TL;DR: Device code phishing turns a legitimate Microsoft sign-in into attacker access after MFA succeeds, according to Doppel. Microsoft identity teams need to treat the device-code flow and the resulting session as attack surface, not proof of user intent.
Editorial analysis by NHI Mgmt Group, based on content published by Doppel: “Six Months of Device Code Phishing Kits: A Field Guide”.
By the numbers:
- Microsoft's September 2026 analysis put 12,000+ inboxes compromised across over 10,000 organizations worldwide.
Key questions
Q: Why do passwords, MFA, and passkeys fail to stop device code phishing?
A: They fail because the user completes a legitimate sign-in inside the identity provider, so the attacker receives a valid token rather than stealing the factor itself.
Q: What are the signs that a device-code sign-in is malicious?
A: Look for an unexpected device-code event, a resource the user did not intend to access, unfamiliar source IPs or hosting providers, and rapid follow-on actions such as mailbox rule creation or Graph activity.
Q: What should teams do immediately after they suspect device code phishing?
A: Disable the account, revoke active sessions, and inspect mailbox and authentication settings before closing the incident.
Practitioner guidance
- Block device code flow where business use does not require it Use Conditional Access to disable device code flow for general users, then document narrow exceptions for shared devices or legacy workflows that truly need it.
- Rewrite user training around session intent Teach employees to ask whether they started the sign-in on a device they recognise, not whether the final Microsoft page looks legitimate.
- Correlate device-code sign-ins with post-authentication behaviour Investigate mailbox rules, Graph reconnaissance, device registration, unfamiliar IPs, and unusual resource access immediately after a device-code event.
Bottom line: Device code phishing abuses a real Microsoft sign-in flow, so a legitimate domain and a successful MFA prompt do not prove legitimate intent.
Glossary terms: Device code phishing, Device Authorization Grant, Phishing-as-a-service, Session Token Exposure
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Session origin, not MFA outcome, is the real control boundary: device code phishing succeeds because identity programmes still overvalue a successful login event as proof of legitimate intent. The authentication step can be genuine while the session origin is malicious, which means the control failure is upstream of token issuance. Practitioners should treat the start of the flow as the security decision point, not the password or MFA prompt.
A few things that frame the scale:
- Tycoon 2FA alone accounted for 62% of phishing detected by Microsoft and over 64,000 confirmed incidents.
A question worth separating out:
Q: How should organisations decide whether to allow device code flow?
A: Allow it only where a real workflow depends on it and the devices involved cannot use stronger methods. For most users, the safer default is to block the flow, because the protocol’s convenience also creates a clean handoff path for attacker-initiated sessions.
👉 Read our full editorial: Device code phishing turns legitimate sign-in into attacker access