1. News
  2. Alerts
  3. Microsoft 365 · Hacking
AlertMicrosoft 365 · Hacking3 min read

Hackers steal Microsoft 365 logins that already passed the code check

Attackers are copying Microsoft 365 sign-ins after the password and code check, then using them to take over email at 79 organizations.

By the Dashline deskSource: The Hacker News
Hackers steal Microsoft 365 logins that already passed the code check
Photo: Sebastiaan ter Burg from Utrecht, The Netherlands, CC BY-SA 2.0
Act this week
What happenedAttackers used fake Microsoft sign-in pages to steal login sessions, then replayed them to break into email accounts without needing the password again.
Who is affectedOrganizations using Microsoft 365 and Entra, especially small businesses whose staff handle payroll, deposits and bonuses by email.
What to do
  1. 1Sign out all sessions and reset the password for any account you suspect.
  2. 2Review each account's sign-in methods and remove any authenticator app you do not recognize.
  3. 3Check inboxes for odd rules with names like a single dot or letter, and look at the list of registered devices.
  4. 4Ask your IT provider to set Conditional Access rules that require MFA everywhere and limit device-code sign-ins.

Hackers are stealing Microsoft 365 sign-ins after the victim has already typed the password and the security code. Security firm Huntress saw 97 accounts hijacked at 79 organizations between July 14 and September 22, 2026. The thieves then got into email without needing to pass the code check a second time.

What happened

Victims land on a fake sign-in page that sits between them and the real Microsoft page. It passes the password and code along, so the sign-in works. Microsoft then issues a token, a digital proof that you logged in. The attackers grab it and replay it from their own devices within minutes. Huntress calls this token spraying.

Huntress counted 497 successful sign-ins out of more than 200,000 login attempts. The stolen tokens came from fake sign-in pages, device-code phishing (tricking someone into approving a sign-in on a code screen) and social engineering during a real login.

How the attackers stayed in

A stolen token can expire or be cancelled. So the attackers added their own authenticator app to the account. At no fewer than 19 organizations, the victim's existing code methods were removed and a new one added within three hours. In one case on July 21, an app named "iPhone 13" was activated less than 51 minutes after the hijack.

They also registered at least 48 fake computers in victims' Microsoft directories. Huntress says a registered device can give attackers a longer-lasting way to request tokens, and it stays listed until someone deletes it.

The hidden inbox rules

The attackers also set up inbox rules with odd names such as a single dot, "sss" and "d". These rules deleted mail containing words like payroll, deposit and bonus, or moved it to obscure folders such as RSS Feeds. That kept the mailbox owner from seeing the messages.

In one mailbox, a rule marked every incoming message as read and deleted it. The account was then used to send spam to hundreds of outside recipients before Microsoft's Entra ID Protection rated it high risk.

Who it affects

The report covers organizations that use Microsoft 365 and Entra, Microsoft's system for work accounts and devices. Small businesses where staff handle payroll and deposits by email have the most reason to check. The material does not describe attacks on personal home accounts.

What to do

The alert box above lists the steps. Huntress adds that Conditional Access policies, which are rules an administrator sets to control how people may sign in, can close gaps that codes alone leave open. They should require a code check, or block the sign-in, for all users, all apps and all app types, with no exceptions.

What is not known

The material does not say who is behind the campaign or how many more organizations may be hit. Huntress traced more than 200,000 failed login attempts to one range of internet addresses. It did not say whether the attacks have stopped.

The takeaway

A code check at sign-in is not enough on its own, so review sign-in methods, devices and inbox rules on Microsoft 365 accounts now.

More articles

You should really read these.

Next step

Let’s talk