If your office runs Microsoft 365, a late October Huntress report is worth a calm, same-week look. Attackers stole sign-in sessions after people finished multi-factor authentication, then reused those sessions from their own machines. MFA still matters. A stolen session token can keep working until someone revokes it and cleans up what the attacker left behind.
Huntress tracked the campaign from July 14 to September 22, 2026, and published on October 22. Researchers responded at 79 organizations, saw at least 497 successful sign-ins against more than 200,000 failed attempts, and found at least 48 rogue Entra devices, wiped and replaced MFA methods, and short-named inbox rules used to hide mail. In one case, a compromised mailbox sent a payroll-related message outside the company.
Here is what that means in plain language and a short checklist for whoever manages your Microsoft 365 tenant.
What Huntress Reported
Instead of guessing passwords, the attacker replayed stolen "proof of login" tokens at volume. Huntress calls that pattern token spray and replay. Tokens came from adversary-in-the-middle relays between the victim and Microsoft's real sign-in page, from device-code phishing, and from social engineering during a legitimate login. Because the token is issued after MFA succeeds, whoever holds it does not need to pass MFA again for that session.
Replay traffic came from IP addresses tied to German hosting provider 1337 Services GmbH. Microsoft Entra ID Protection flagged several of those addresses as known threat-actor infrastructure.
After getting in, the attacker dug in. Huntress saw fake computers registered in Entra directories (often named DESKTOP- plus eight hex characters), MFA methods cleared and replaced with an authenticator the user did not set up, and forgettable inbox rules that moved mail to RSS Feeds or Conversation History, or hid payroll and bank terms. A password reset alone does not remove those devices or MFA methods, and it does not always kill an already-issued access token. Sessions need to be revoked too.
Why MFA Alone Is Not Enough
Multi-factor authentication still stops a huge share of simple password theft. This campaign shows the next step when MFA works: steal the session MFA just approved, then reuse it from somewhere else.
That matters for small offices because email, files, and payroll often live in the same Microsoft 365 tenant. Day-to-day computer security now includes watching what happens after a successful sign-in, not only whether MFA is on. Conditional Access can require the right device, block risky client flows, and stop a replayed token from reaching mail and files. Huntress noted that in one busy phase, more than a thousand blocked sign-ins came from just four organizations with Conditional Access working, while dozens of other tenants without that barrier saw successful sign-ins.
You do not need to be a large enterprise to be scanned. Account hygiene is the story this week.
Five Calm Checks for This Week
Hand this list to whoever manages your Microsoft 365 or Entra admin center, or to your IT provider.
- Revoke sessions, then reset the password. A password reset alone does not invalidate every access token and does not remove attacker-registered devices or MFA methods.
- Audit Entra devices. Look for unfamiliar computers, especially names like DESKTOP- followed by eight hex characters, or devices joined from hosting addresses nobody in your office uses.
- Audit MFA methods. Confirm each person still recognizes every authenticator and phone number on the account. Remove anything that appeared after a suspicious sign-in.
- Review inbox rules. Check for one- to three-character or punctuation-only names, rules that move mail to RSS Feeds, RSS Subscriptions, or Conversation History, and rules keyed on payroll, direct deposit, bank, or bonus.
- Tighten Conditional Access and device-code flow. Require MFA (or block access) for all users, all cloud apps, and all client app types where your licenses allow it. Restrict device-code flow unless a documented tool truly needs it. For managed Microsoft 365 setups, also keep reviewing which apps hold keys to mail and files.
If Microsoft 365 is outside your usual comfort zone, send one clear note to your IT provider with this checklist attached.
If Something Already Looks Wrong
If you already see unrecognized Entra devices, MFA methods nobody set up, short-named inbox rules, or sign-ins from hosting providers your staff never use, treat it as an incident. Preserve logs when you can, revoke sessions, reset passwords, remove rogue devices and MFA methods, review mailbox activity, and bring in whoever can investigate properly.
A Calm Local Takeaway
Huntress's token-replay report is a prioritization signal, not a prediction that every Georgia or South Carolina office is already compromised. If you run Microsoft 365, confirm sessions can be revoked quickly, review devices and MFA methods, scan inbox rules, and ask whether Conditional Access is doing real work. MFA remains worth having. Session theft means the work does not stop at the second factor.
Whether your office is in Canton, GA or South Carolina, a same-week session and MFA check beats finding out from a missing payroll reply or a rule that hid the warning.
Rhinotech has helped SMBs across North Atlanta and Upstate South Carolina keep technology working since 2011. For our managed Microsoft 365 clients, we already review connected apps so unused or risky access does not linger. We are happy to help you review recent sign-ins, revoke sessions, check devices and MFA methods, and look for odd inbox rules. If you are not sure what Conditional Access or device-code settings you have today, a free tech checkup is a simple place to start. We will walk through it with you, calmly and in plain language.
