One copied “booking reference” opened a cloud session the employee never meant to grant. In mid-October 2026, a construction-sector worker followed a spear-phishing lure into a fake Microsoft Teams meeting scheduler, treated a device user code as ordinary meeting logistics, and entered it on Microsoft’s real device-login page. That single approval authorized the attacker’s session and issued tokens, including a Microsoft Authentication Broker session, on a Microsoft 365 account with no MFA enrolled. According to Huntress, the SOC contained the intrusion before further escalation, and no wider victim count or company name has been published.
How a typosquat turned into a Teams booking lure
Spear-phishing mail arrived from a typosquatted domain that impersonated a senior vice president at another construction firm. Huntress reports the link path used redirects, including Google short links and Safe Links style hops, before the browser landed on a page dressed as a Teams meeting scheduler. The page did not need a crude password form. It silently started a real Microsoft device-code authorization and showed the user code as a booking reference.
Confirm Meeting copied that code to the clipboard and pointed the victim at Microsoft’s genuine device-login experience. The employee was not staring at an obvious lookalike password box. The next step looked like finishing a calendar task on a trusted Microsoft property. Huntress framed the craft clearly: device code phishing already works because it rides the legitimate device-code workflow, and this incident pushed the chain further by wrapping that workflow in everyday meeting-booking context.
Huntress had already tracked large device-code phishing activity earlier, including a Railway-based Microsoft 365 token-replay wave often built around PDF lures and a verification prompt on the real Microsoft device login URL. The construction case is not that campaign. It is the same class of authorization abuse, restyled so the code feels like a booking ID instead of a security challenge.
What the victim actually approved on the real login page
Device-code phishing depends on the victim completing Microsoft’s own device-login ceremony for a session the attacker started. The employee opened microsoft.com/devicelogin (the legitimate device-login path), pasted the code that the fake scheduler had labeled a booking reference, and approved access. Because the domain was real, browser cues that catch many spoofed password pages did not fire the way defenders hope.
No MFA was enrolled on the compromised Microsoft 365 account. Acceptance of the code led Microsoft to issue session tokens to the attacker’s side of the flow, including a Microsoft Authentication Broker session. From that point the problem was no longer “guess the password.” It was a live cloud session the victim had authorized under false context.
Huntress has not named the construction firm, has not attributed a threat actor group, and has not published victim counts beyond this contained account. The public record stops at one Microsoft 365 identity stopped before lateral movement or data theft was documented.
| Step | What the employee saw | What actually completed |
|---|---|---|
| VP-style construction outreach | Typosquatted spear-phish | |
| Landing page | Teams meeting scheduler | Attacker-started device-code flow |
| Code label | Booking reference | Microsoft device user code |
| Approval site | Real Microsoft device login | Attacker session authorized |
| Outcome | Meeting confirmed | M365 tokens issued, no MFA on account |
Why a meeting-shaped code beat ordinary caution
People paste booking codes all day. The lure did not ask for a password on a shady lookalike. It asked for the same kind of short string staff already treat as calendar plumbing, then sent them to a genuine Microsoft URL to “confirm.” That combination collapses the usual mental checklist: wrong domain, odd password field, unexpected MFA prompt.
The attacker never needed to intercept a typed OTP on a proxy page. The attacker never needed to intercept a typed OTP on a proxy page in this incident. The victim finished Microsoft’s device-code grant for someone else’s session. Tokens followed, including broker material useful for staying attached to the cloud identity. Huntress states the SOC moved fast enough that the story ends at containment, not a ransomed build site or a dumped file share. Speed after the fact is not the same as stopping the grant.
Construction firms live in shared inboxes, subcontractor threads, and constant meeting reshuffles. A VP-flavored invite from “another firm on the job” is normal traffic. Typosquatting plus a scheduler UI exploits that normalcy. The same pattern scales whenever device-code grants remain easy for users to complete without a strong, already-enrolled factor bound to the real user and the real client.
Defenders who only hunt for fake password fields will miss this path. The valuable signal is unexpected device-code completions, odd Authentication Broker sessions, and mail that drives users to paste codes into microsoft.com/devicelogin after third-party “booking” pages. Huntress’s key takeaway matches the mechanics: actors are adapting device-code phishing into social-engineering plays that disguise authorization as an everyday task.
how blocking Microsoft device-code grants stops this workforce lure.
FAQ
How did the construction firm Microsoft 365 account get compromised?
The construction firm Microsoft 365 account was compromised when an employee entered a device user code from a fake Teams meeting scheduler into Microsoft’s real device-login page. According to Huntress, that approval authorized the attacker’s session and issued tokens, including a Microsoft Authentication Broker session, on an account with no MFA enrolled. The intrusion was contained before further escalation was reported.
What made the fake Teams scheduler different from a normal phishing page?
The fake Teams scheduler differed because it did not need the victim to type a password into an attacker-hosted form. Huntress describes a page that started a real Microsoft device-code flow, labeled the user code a booking reference, copied it for the user, and sent them to the genuine Microsoft device-login URL to finish authorization. The trust cues of a real Microsoft domain did the heavy lifting.
Did Huntress name the company or the threat actor?
Huntress did not publish the victim company name, a named threat actor, or a victim count beyond the single contained Microsoft 365 account. The disclosure centers on the mid-October 2026 construction-sector incident path and the booking-flow disguise around device-code phishing.
Is this the same as the earlier Railway device-code campaigns Huntress tracked?
This construction incident is not the same event as the earlier Railway-based Microsoft 365 token-replay device-code campaigns Huntress described. Huntress presents the Teams booking-flow lure as an evolution of that broader device-code phishing tradecraft, still relying on victims approving codes on the real Microsoft device-login path, but packaged as meeting logistics instead of a plain verification prompt.
What should IT watch after a suspicious “booking code” click?
IT should treat unexpected device-code approvals and new Microsoft Authentication Broker sessions as first-class alerts, revoke those sessions immediately, and inspect mail that drives users from third-party scheduler pages to microsoft.com/devicelogin. In the Huntress construction case, fast containment limited impact to one account; the preventive question is whether users can still complete attacker-started device-code grants at all.