ITSecurityGuru

Token-replay campaign hijacks 97 Microsoft 365 accounts as Huntress extends SOC response across Defender


Huntress has expanded its Agentic Security Platform so that its 24/7 security operations centre (SOC) can investigate and respond to incidents raised across the wider Microsoft Defender suite, not only Defender for Endpoint and Defender Antivirus.

The move follows a token-replay campaign that Huntress tracked between 14 July and 22 September 2026, which compromised 97 Microsoft 365 accounts across 79 organisations.

The attackers used adversary-in-the-middle (AiTM) phishing to capture session tokens after victims had completed multi-factor authentication, then replayed those tokens to access accounts without a password or a further MFA prompt. Once inside, they registered rogue devices and authenticator apps and set up inbox rules to hide their activity. In one case, a hijacked mailbox was used to send a payroll-related email to an external accountant.

Huntress Managed ITDR detected the activity first, and Microsoft Entra ID Protection flagged the same attacker infrastructure. Huntress says the campaign prompted it to rebuild its detection pipeline so that a single incident naming several accounts is attached to each affected identity.

The identity angle is central to the update. Huntress reports that in a recent two-week period, 85% of medium- and high-severity Defender incidents it saw carried no device-related evidence at all, meaning endpoint-centric tooling would have missed them.

Under the expanded integration, Huntress now ingests incident data from:

  • Microsoft Defender for Identity
  • Microsoft Defender for Office 365 (for example, phishing emails caught at the gateway)
  • Microsoft Defender for Cloud Apps (for example, risky OAuth applications)
  • Microsoft Entra ID Protection (for example, compromised-account verdicts)

Huntress analysts correlate these signals, prioritise the queue, confirm whether a threat is active and respond, before sending customers a report on what happened and what action was taken. Incidents are attached to the endpoints involved, the identities named, or both.

Analysts can also run advanced hunting queries against a customer’s own Microsoft tenant data, going back up to 30 days, to trace process trees, look for the same tooling on other devices, or review what an account did after a suspicious sign-in. Huntress applies its own per-tenant query limits so that its hunting does not exhaust the Microsoft API quota shared with other security tools.

“Attackers don’t care how big a company is, and neither should the quality of its defence,” said Adam Bates, Vice President of Product Management at Huntress. Bates added that Huntress integrates with the Defender Suite because organisations of every size need defence in depth, and that Defender signal helped uncover the token-replay campaign.

The capability is aimed at organisations licensed for Microsoft 365 E5 or Defender Suite for Business Premium that want round-the-clock response without building in-house capacity to triage Defender alerts. Existing customers whose Microsoft tenant and Defender for Endpoint are already connected to Huntress receive the expanded data automatically.

Huntress also highlighted a new Adversary Infrastructure capability within Managed ITDR, which converts one organisation’s incident into a same-day Conditional Access block across eligible, opted-in Entra ID P1 tenants.



Source link