Device-code phishing

Device-code phishing tricks a person into authorizing an attacker-initiated OAuth device authorization request, allowing the attacker-controlled client to obtain tokens for the access granted.

A real sign-in page can authorize the wrong client

The device authorization grant separates the browser where someone approves access from the client that receives the tokens. In a phishing attempt, the attacker starts that client request and persuades someone else to approve it.

The code the person enters is the user_code. The attacker’s client holds a separate device_code and uses it to collect the tokens after approval. The browser can be on a genuine sign-in site throughout.

A meeting lure asks you to enter a code

A fake invitation may send an employee to a genuine sign-in page with a supplied code. The employee thinks they are joining a meeting but authorizes the attacker’s client instead. Microsoft documented meeting-invitation lures in its February 2025 Storm-2372 report.

Check the request, not just the domain

Ask whether the person started the sign-in and recognizes the app requesting access. Match the lure to authorization activity, the requested app, and later resource operations. Token issuance alone does not tell you whether someone read a document or mailbox.

Microsoft recommends restricting device-code flow to necessary uses while accounting for legitimate clients. If compromise is suspected, check both tokens and application sessions during containment. A password change alone does not show that all access has ended.

Sources

See it in practice