Theory · 10 min · Email and phishing analysis
Phishing that beats MFA
Recognise AiTM, device code and consent phishing in the sign-in logs.
Adversary-in-the-middle (AiTM) phishing puts a reverse proxy between the user and the real sign-in page. The user passes MFA for real; the proxy keeps the session cookie and the attacker replays it. Microsoft reported one such campaign that targeted more than 10,000 organizations from September 2021 onward.
Device code phishing abuses a legitimate flow for devices without a keyboard (RFC 8628). The attacker starts a sign-in, gets a code, and asks the victim to enter it on the real Microsoft page. The victim signs in the attacker’s session. Microsoft reported Storm-2372 using it since August 2024.
Consent phishing asks the user to grant an application access to mail or files. No password is stolen; the app’s token does the work.
All three pass MFA. The signals are elsewhere: an unfamiliar IP or hosting provider right after the click, a new user agent, a device code sign-in nobody expected, a newly consented app.
Your turn: match observations. Which kind of phishing is each?
Do the interactive check Free, in the browser.
Sources
- From cookie theft to BEC: attackers use AiTM phishing sites (July 2022) Microsoft Threat Intelligence
- Storm-2372 conducts device code phishing campaign (February 2025) Microsoft Threat Intelligence
- RFC 8628: OAuth 2.0 Device Authorization Grant IETF
- Incident response playbook: app consent grant investigation Microsoft Learn