The login page is real. The device you are authorizing might not be yours
Device-code phishing exposes a limit of the advice to check the domain: a genuine sign-in can still authorize a session initiated by someone else.
The archive
Sourced guides, explanations and news analysis. Read by question, not by jargon.
Device-code phishing exposes a limit of the advice to check the domain: a genuine sign-in can still authorize a session initiated by someone else.
The trick is not a mysterious button. It is a change of task: a website turns a familiar verification step into permission to run software on your device.
A September Microsoft report illustrates why the name of a security feature cannot substitute for understanding the action a message asks you to approve.
Microsoft's September 22 report describes more than polished phishing messages. Our analysis asks what changes when compromised correspondence reveals how an organization makes decisions.
A reporting culture is built in ordinary replies, not awareness posters. Make it possible to say what happened before someone knows how serious it is.
When a call sounds like someone you know, the safest question is not whether you can hear an AI artifact. It is how to check the request outside that call.
Passkeys and security keys are valuable controls. Understanding their scope helps explain why account recovery, consent and payment decisions still matter.
Account recovery asks support staff to restore trust precisely when a normal proof is missing. That decision needs a designed process, not a test of confidence.
A deadline becomes dangerous when it is used to replace verification, isolate a decision or excuse a change in process.
Social engineering often succeeds before the dangerous request arrives. A plausible role and a familiar process can do much of the work.