TL;DR: After MFA succeeds, attackers can still retain access through stolen session cookies or tokens, Doppel says in case work on Microsoft 365 phishing kits. Session revocation and token invalidation become the real containment step, because the login itself may already look legitimate.
Editorial analysis by NHI Mgmt Group, based on content published by Doppel: “Anatomy of an Active Microsoft 365 Phishing Kit”.
Key questions
Q: Why do AiTM phishing kits still succeed against MFA?
A: AiTM kits succeed because they capture the authenticated session, not just the password.
Q: What signs show that a phishing campaign is using session theft rather than password reuse?
A: Look for a normal-looking login followed by mailbox rules, app grants, token reuse, device registration, or access from an unexpected client without repeated password prompts.
Q: What breaks when MFA is bypassed by token theft instead of password compromise?
A: The control that breaks is the assumption that a successful sign-in proves ongoing trust.
Practitioner guidance
- Map the compromise to the captured artefact Determine whether the incident involved a password, a session cookie, or an authorization token, because containment and evidence differ for each.
- Revoke active sessions and refresh tokens Use provider guidance to invalidate current access, then verify whether mailbox, file, and app activity stops before assuming the account is clean.
- Harden or block device-code flows Block the flow where the business does not need it, and scope any exception to known use cases with monitoring around approval events.
Bottom line: Microsoft 365 phishing kits can produce attacker access even when the victim completes MFA, because the real target is often the session, not the password.
Glossary terms: Adversary-in-the-middle phishing, Persistent Cookie, Device code phishing, Phishing-as-a-service
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Session theft, not password theft, is the decisive failure mode in Microsoft 365 phishing kits. Once the kit captures a usable session cookie or token, the attacker inherits the authenticated result rather than the credential itself. That shifts the control question from password strength to session-bound trust, which is why incident handling must follow the post-authentication artefact. Practitioners should treat the session as the unit of compromise.
A few things that frame the scale:
- The IBM/Ponemon 2025 Cost of a Data Breach Report found that phishing-initiated breaches cost an average of $4.8M each.
A question worth separating out:
Q: What should teams do after credentials are entered into a suspicious sign-in page?
A: Reset the password, revoke active sessions and tokens, review mailbox rules and OAuth app grants, and confirm whether any secondary access was created. Fast containment matters because a relay attack can make the login seem valid even when the credentials were captured by an attacker.
👉 Read our full editorial: Microsoft 365 phishing kits turn completed MFA into account compromise