Device-code phishing tricks someone into approving a sign-in that an attacker started. The victim can be directed to the real verification page of a familiar service.
How it works
Device authorization is a legitimate way for an app or device to sign in using a short code entered in a browser. In the phishing version, the attacker starts the process, sends the code to the target and persuades them to approve it. The resulting authorization can give the attacker’s client access within its permissions.
Why it matters
The page and application name may look legitimate, and the victim may complete their usual multifactor authentication. The danger is approving a request that belongs to someone else, not necessarily typing a password into a counterfeit website.
What you can do
Enter a code only when you started the sign-in yourself and can match it to your device and app. If you approved an unexpected request, contact your security team or provider through a known channel and review unexpected connected-app authorizations and sessions.
For more detail, Microsoft explains observed device-code phishing. Read the GitHub Copilot sign-in research for a related Hacked.com report.
