CyberKit

Device Code Phishing

Also called Device Code Flow Abuse.

Tricking a user into approving an attacker-generated OAuth device code.

What it is

An attack that abuses the OAuth 2.0 device-authorization grant (designed for input-constrained devices like smart TVs) by generating a legitimate device code and social-engineering the victim into entering it and approving the sign-in. That hands the attacker a valid access token without ever phishing a password.

Why it matters

The resulting token comes directly from the identity provider through a legitimate, standards-compliant flow, so it can bypass password-based defenses and look like an ordinary sign-in to defenders. That makes it attractive against MFA-hardened tenants.

In practice

A phishing email tells the target their access is expiring and to visit the real Microsoft device-login page and enter a code, approving it hands the attacker a live session for the account.

What to look for

  • Device code sign-ins for users who never use device flows.
  • A device code login followed by mail or file access from a new IP.
  • Phishing messages asking the user to enter a code on a real login page.

Common mistake

Telling users to check the URL. The page really is the provider's; the code is the trick.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

Read next

  • Conditional Access Bypass: Evading identity policies that gate access by device, location, or risk.
  • MFA Fatigue: Spamming MFA push prompts until the user approves one.
  • Golden SAML: Forging SAML assertions with a stolen identity-provider signing key.

Sources