Device Code Phishing Hijacks Microsoft Teams Sign-In
Attackers used a fake Teams scheduler to trick a construction employee into approving a device code login, granting them account access.
Updated on Nov. 13, 2026 in Cybersecurity

Attackers impersonated a senior vice president at another construction firm and lured an employee to a fake Microsoft Teams meeting page that displayed a device code. The victim's approval gave the attackers a valid session token before Huntress's security operations center identified the incident.
Why it matters
The attack abuses Microsoft's genuine device login flow, so the victim sees the real Microsoft sign-in page and the scheme is harder to spot than a conventional credential-harvesting site. The encrypted phishing kit is built to slip past email scanners and crawlers that do not execute JavaScript.
The phishing kit was delivered as AES-256-GCM ciphertext with its decryption key on the same page, and when Microsoft returned an error the kit started a new device code session. The incident report does not state how many accounts were targeted or how many were compromised.
The players
Huntress
Huntress is a managed security provider whose security operations center identified the incident before the attackers could use the stolen session token.
Microsoft
Microsoft is the technology company that operates Microsoft Teams and the device code sign-in flow that the attackers abused.
The details
The lure was a Google share link that redirected to a page showing an executive's headshot and offering an introductory call about a supply partnership. Clicking Continue started a Microsoft device code request, and the page displayed the code as a Booking Reference with a countdown timer, after which a copy button and a popup opened Microsoft's real sign-in page. After the victim signed in, the page showed a Verification complete note and redirected to a Calendly booking page, while the final login was routed through a residential proxy in New Orleans.
Timeline
Helpnetsecurity.com published its article on the device code phishing incident on November 13, 2026.
The Tech Race
Device code phishing turns Microsoft's OAuth 2.0 device authorization grant, a flow meant for input-limited devices, into a credential-theft vector against standard workplace accounts. The method works because the victim approves the request on Microsoft's own domain, which weakens defenses that rely on spotting fake login pages.
Anyone who receives a meeting invitation or a link to a sign-in page should verify the sender's domain and avoid entering a code shown on a web page into a Microsoft login prompt. Administrators can reduce exposure by reviewing whether device code sign-in is needed for their tenant and restricting it where it is not.
The takeaway
Treat any unexpected request to enter a code on a sign-in page as suspicious, even when the page appears to be Microsoft's own, because approving a device code grants the requester access to the account.
Further reading
For more on how attackers exploit trusted login flows, see the Cybersecurity section.
Source note: This article includes information reported by Help Net Security.



