Cyberuptive

Microsoft 365 Session Theft: Why MFA Isn't Enough

By Chuck Lerch, Founder and CEO, Cyberuptive ·

Yes, attackers can get into Microsoft 365 with MFA turned on. Session-theft attacks wait for the user to complete MFA, then take the signed-in session that results. The fix is a set of identity controls: block device code sign-in, move high-risk users to phishing-resistant MFA, bind sessions to managed devices, and monitor for new devices and inbox rules around the clock.

If your Microsoft 365 security plan ends at "we turned on MFA," you are protecting the front door while attackers walk in through the session behind it. This guide explains the problem in plain terms, gives you a self-check you can run on your own tenant this week, and lays out the controls we recommend in priority order.

What are the key takeaways?

  • MFA isn't the finish line. Session theft happens after a successful MFA prompt, so a completed prompt doesn't prove the session is safe.
  • Device code sign-in is the easiest path to close. Microsoft recommends blocking it wherever possible (Microsoft Learn).
  • Phishing-resistant MFA stops look-alike sign-in pages but not device code phishing, so you need both controls.
  • A password reset alone won't remove an attacker holding a valid session.

Why is session theft getting worse now?

Session theft used to take real skill. Researchers at Huntress and Microsoft have both documented phishing-as-a-service platforms that sell Microsoft 365 session theft as a subscription. The best-known example, EvilTokens, reached roughly 12,000 inboxes at 10,000 organizations before Microsoft and Health-ISAC took down its infrastructure in September (Microsoft). The service even used AI to read stolen mailboxes and work out who in each company could approve payments.

The takeaway for a business owner: you aren't being targeted by a rare, elite attacker. You are being targeted by a product, and anyone willing to pay a monthly subscription can buy it.

How does Microsoft 365 session theft work?

Think of signing in to Microsoft 365 like checking into a hotel. Your password and MFA are the ID you show at the front desk. The session token is the room key you get back. Nobody checks your ID again when you use the key. Session theft is stealing the key.

Attackers use a real Microsoft feature against you. Microsoft supports a sign-in method called device code flow for smart TVs and conference room systems that don't have a keyboard. The device shows a short code, and you enter it on Microsoft's real website from your phone or laptop. Attackers send a convincing email, often a fake shared document or Teams invite, with a code they generated themselves. Your user goes to the genuine Microsoft page, enters the code, and approves MFA. The attacker's computer gets the room key. Nothing about the experience looks suspicious, which is why Microsoft labels device code flow "a high-risk authentication method" (Microsoft Learn).

Attackers stand in the middle. The attacker hosts a look-alike sign-in page that quietly passes everything through to Microsoft in real time. Your user signs in and approves MFA, Microsoft issues the key, and the attacker's page keeps a copy.

Once attackers have the key, they move fast. Microsoft found that some EvilTokens operators registered their own device to the account within 10 minutes, giving themselves a way back in even if the original key stops working (Data Breach Today). From there, the usual goal is business email compromise: reading invoices, creating hidden inbox rules, and sending payment-change requests from a real, trusted mailbox.

How can you check your Microsoft 365 tenant in 15 minutes?

If you have admin access to Microsoft Entra ID, you can answer these questions today. Every "no" or "not sure" is a gap.

  1. Is device code flow blocked? Check Conditional Access for a policy that blocks the device code authentication flow. Microsoft offers a ready-made managed policy for this (Microsoft Learn). Tenants created after July 1, 2026 block it by default through security defaults, but older tenants usually don't (Microsoft Learn).
  2. Who is actually using it? In the sign-in logs, filter on Authentication protocol = Device code flow. If you see sign-ins from people who don't manage conference room hardware, investigate them.
  3. Can your MFA be relayed? Push notifications, text codes, and authenticator codes can all be passed through a look-alike page. Passkeys, FIDO2 security keys, and Windows Hello for Business can't, because they only work on the real Microsoft domain. Check what share of your users, especially admins and finance staff, use these phishing-resistant methods.
  4. Do you require managed devices? A Conditional Access policy that requires a compliant or Entra-joined device for email and files makes a stolen key much harder to use from an attacker's laptop.
  5. Would you notice a new device or inbox rule? Ask who gets alerted, and how fast, when a user registers a new device, adds an MFA method, or creates a forwarding rule. If the honest answer is "nobody until Monday," that is the gap attackers rely on.

Which controls should you put in place first?

You don't have to do everything at once. This is the order we use with clients because it closes the most risk for the least disruption.

PriorityControlWhat it stops
1Block device code flow, with narrow exceptions for conference room devices. Test in report-only mode first (Microsoft Learn).The easiest session-theft path
2Move admins and finance staff to phishing-resistant MFALook-alike sign-in pages that relay MFA
3Require compliant devices for Exchange, SharePoint, and TeamsReplay of stolen keys from unmanaged machines
4Turn on Token Protection where supported (Microsoft Learn)Stolen keys used from a different device
524/7 monitoring of identity and mailbox changesAttacks that get past the first four layers

None of these controls replaces the others. Phishing-resistant MFA stops look-alike pages but not device code phishing, because in that attack the user really is on Microsoft's site. That is why priority 1 comes first.

What should you do if a session has already been stolen?

Speed matters more than perfection. Our incident responders work in this order:

  1. Cut the session, not just the password. Microsoft warns that access can survive a password reset unless sessions and tokens are revoked (Microsoft), and that revocation may not take effect instantly (Data Breach Today). Temporarily disabling the account is often the safest first move.
  2. Remove what the attacker added. Look for new devices, MFA methods, app consents, and inbox or forwarding rules created around the time of the suspicious sign-in.
  3. Check what left the mailbox. Review sent items and message traces for phishing or payment requests sent to customers and vendors, and warn them directly if you find any.
  4. Stay alert after cleanup. Watch the account for repeat sign-ins over the following weeks. These services are built to come back.

How does Cyberuptive help stop session theft?

Cyberuptive is a managed security services provider headquartered in Honolulu, protecting organizations across the US, Canada, Europe, and Asia-Pacific. Our Microsoft 365 and Azure security team runs the self-check above for you, then puts the priority controls in place without breaking conference rooms or your users' day. Our US-based SOC and managed detection and response service watches for new devices, new MFA methods, risky sign-ins, and suspicious inbox rules around the clock, and contains compromised sessions under response rules you approve in advance. If you think an account is already compromised, our incident response team can help you contain it and find out what the attacker touched. For related guidance, see which Microsoft 365 logs to keep.

What else should buyers and operators know?

Does MFA protect Microsoft 365 from phishing?

MFA stops password-only attacks, but not session theft. In session theft, the user completes MFA and the attacker takes the signed-in session afterward. Phishing-resistant MFA and blocking device code flow close the two main paths.

What is a Microsoft 365 session token?

It is the digital proof Microsoft issues after a successful sign-in so users don't have to sign in again for every email or file. If it is stolen, the attacker can use the account as that user.

What is device code phishing?

It is an attack that tricks a user into entering an attacker's code on Microsoft's real sign-in page. The user signs in normally, and the attacker's device receives access to the account.

Will resetting a password remove an attacker?

Not by itself. Microsoft says access can persist after a reset unless sessions and tokens are also revoked (Microsoft). Revoke sessions, consider disabling the account temporarily, and remove any devices, MFA methods, or inbox rules the attacker added.

Is a small business likely to be targeted?

Yes. These services run campaigns at scale. Microsoft lists EvilTokens victims in wholesale distribution, construction, financial services, real estate, higher education, and healthcare (Microsoft).

What is the next step for your organization?

Find out where your tenant stands against session theft before an attacker does. Book a Microsoft 365 identity review or call 833-92-CYBER to talk through your current controls.