THE UNDERGROUND FILES | Reviewed November 17, 2026 — Huntress’ investigation of a Microsoft 365 token-replay campaign demonstrates a distinction that matters during account recovery: changing a password and removing an intruder’s remaining access are not necessarily the same operation. This is a retrospective case study, not a claim that the campaign began today.
The documented campaign
Between July 14 and September 22, Huntress recorded at least 497 successful sign-in events across 79 customer organizations, alongside more than 200,000 failed attempts. The researchers describe replay of stolen authenticated sessions obtained through phishing and related deception. The successful-sign-in count is not a count of 497 separate victims.
The investigation identified at least 48 unauthorized Entra devices, replacement authentication methods and inbox rules that concealed communications. In one case, the intruder used a mailbox to send a payroll-related message. These are observations within the researcher’s monitored environments, not a complete worldwide victim census.
Why the next sign-in matters
Huntress explains that an attacker-registered authentication method or device may remain after a password change. Its response guidance calls for revoking sessions, resetting passwords, removing unauthorized devices and authentication methods, and examining mailbox rules. Its October retrospective also recommends appropriate Conditional Access controls.
IPCRIME analysis: recovery is a sequence
A useful incident review asks three different questions: what originally allowed access, what the intruder changed afterwards, and what still grants access now. A control addressing only the first question can leave the second and third unresolved. An unexpected authentication method deserves investigation even if the account’s password was just replaced.
That does not make multifactor authentication pointless. It means defenders must consider the lifecycle of authenticated sessions and the authority to register new access methods. Treat a suspicious device or mailbox rule as a lead to validate against legitimate administrative activity, rather than deleting records indiscriminately.
For an investigation record, preserve the chronology of sign-ins, session revocation, authentication changes and mailbox activity. Explain separately which actions are confirmed, which messages were sent, and whether any financial loss has actually been established. A plausible route to fraud is not itself proof that money was lost.
Original research
Huntress’ token-replay campaign investigation
Huntress October 2026 threat retrospective
Research-based case analysis. IPCRIME has not inspected affected tenants or independently validated the vendor’s incident telemetry. Featured image is conceptual artwork.

[…] a related investigation perspective, see IPCRIME’s Microsoft 365 token-replay case file. Keep observations from separate incidents distinct when using them to improve a response […]