Teams booking flow used for Microsoft device code phishing (Huntress)
Huntress reports a fake Teams meeting scheduler that tricked a user into approving a Microsoft device code sign-in; restrict device code flow.
- Published
- Updated
- Ecosystem
- Enterprise softwareWebsites and CMS
- Exploitation
- Yes, Huntress reports its SOC saw the attack against a construction sector company in mid-October and contained it; Help Net Security says a valid session token was obtained
What happened
Huntress reported that in mid-October its SOC saw a device code phishing attack disguised as a Microsoft Teams meeting-booking process. The target was a company in the construction sector. Huntress
Device code phishing abuses the real Microsoft device sign-in flow. The attacker starts a sign-in request and persuades the victim to enter the resulting code on Microsoft’s genuine device login page. The victim completes MFA if prompted and unknowingly authorizes the attacker’s session, which gives the attacker access tokens. Huntress
The reported attack chain:
- Lure email. A spear-phishing email impersonated a senior vice president at a real construction company, using a typosquatted email domain. Huntress
- Link path. Huntress says the link led through several redirects to the phishing site. Huntress Help Net Security says the link went to a Google share link, which redirected to the lure page, and that the attacker’s domain never appeared in the email body, so the message got past URL reputation checks. Help Net Security
- Fake scheduler. The page presented a “Microsoft Teams Meeting Scheduler” asking for a call duration, date and time. Behind the scenes, these steps started a Microsoft device code sign-in and generated a user code. Huntress
- Code shown as a booking reference. Help Net Security reports the code was displayed as a “Booking Reference” with a countdown timer. Help Net Security
- Clipboard and sign-in. Clicking “Confirm Meeting” copied the code to the clipboard and opened a pop-up to Microsoft’s real device sign-in page, where entering the code completed the attack. Huntress
- Evasion details. Help Net Security reports the kit was delivered as AES-256-GCM ciphertext with the key in the same page, which targets scanners that do not run JavaScript. It also reports that the kit retried with a fresh device code if Microsoft returned an error, and that the final login came through a residential proxy in New Orleans. Help Net Security
The outlets differ on the outcome. Huntress says its SOC quickly contained the attack. Huntress Help Net Security says the attackers obtained a valid session token before Huntress identified the incident. Help Net Security The number of other victims, the attacker’s identity and the full timeline are not confirmed in the sources. The Huntress text available to us was truncated, so details beyond the portion quoted here are not confirmed.
Am I affected?
No CVE or software flaw is involved. The sources describe abuse of the legitimate Microsoft device code authorization flow, not a product vulnerability, and no patch is mentioned.
You may be exposed if your Microsoft 365 tenant allows device code authentication and users could receive convincing meeting or business-partnership lures. Huntress notes that many earlier device code phishing attacks used a generic “verification code” pretext tied to a PDF, whereas this one used a meeting-booking flow to set context. Huntress
Signs to look for in sign-in logs: Help Net Security says programmatic user agents such as python-requests or node appearing in interactive sign-in logs point to automated attacker infrastructure. The article does not attribute this indicator to Huntress. Help Net Security
What to do now
- Check whether your business needs device code authentication. If not, restrict it through conditional access; if it is needed, monitor it. Help Net Security
- Tell users to treat any unexpected device code prompt as suspicious, as Huntress advises, even when it follows a plausible meeting-booking step. Help Net Security
- Consider phishing-resistant MFA, and review unfamiliar device sign-ins, as Huntress recommends. Help Net Security
- Search interactive sign-in logs for programmatic user agents such as python-requests or node. Help Net Security
- After a confirmed compromise, check for rogue MFA methods, unknown registered devices, unauthorized app consents, suspicious mailbox rules and suspicious outbound mail. Help Net Security
Update, 18 November 2026
- Help Net Security says that once the attacker’s backend registered a successful sign-in, the lure page closed the popup, showed a “Verification complete” note and redirected the victim to a Calendly booking page so nothing looked out of place. (helpnetsecurity.com)
- Help Net Security says the fake scheduler page showed the impersonated executive’s headshot and offered an introductory call about a long-term supply partnership. (helpnetsecurity.com)
- Huntress published its write-up on November 12, 2026, crediting Andrew Brandt for contributions to the investigation. (huntress.com)