Overview
Modern phishing kits are moving beyond simply stealing usernames and passwords and are increasingly designed to capture Microsoft 365 authentication sessions and tokens. Security researchers have identified kits such as EvilTokens, Knight Office and Kali365 that can capture authentication tokens, replay them into legitimate Microsoft 365 sessions and potentially maintain access even after the victim has successfully completed MFA. This makes session theft an increasingly important identity-security threat for Microsoft 365 environments.
How the Attack Works
Attackers are using several techniques, including device-code phishing, Adversary-in-the-Middle (AiTM) attacks and direct token theft. Device-code phishing tricks the victim into completing authentication with Microsoft’s legitimate identity service while the attacker captures the resulting authorisation. AiTM attacks proxy the authentication process in real time, allowing the victim to complete MFA while the attacker captures the resulting session information. Once a valid token is obtained, attackers can replay it to access cloud resources and email without necessarily needing the user’s password or another MFA prompt.
Why It Matters
The biggest concern is that successful MFA does not automatically mean the resulting session is trustworthy. An attacker who obtains a valid session token may inherit the access already granted to the user, potentially reaching email, files and other Microsoft 365 services. Modern phishing kits also provide operators with dashboards and automation, effectively turning sophisticated identity attacks into a service that can be deployed by less-skilled criminals.
What Defenders Should Do
Security teams should investigate the complete identity attack chain, rather than focusing only on the original phishing message. Look for successful sign-ins from unusual cloud infrastructure, device-code authentication, unexpected token refresh activity, newly registered devices or authentication methods, and suspicious mailbox activity such as forwarding rules or outbound phishing. Where compromise is suspected, revoke refresh tokens, remove unauthorised devices and Windows Hello credentials, review authentication methods and investigate mailbox access. Organisations should also restrict or disable device-code authentication where it is not required.
Expert in the Cloud Insight
The identity perimeter has moved beyond passwords and MFA to the session itself. Microsoft 365 security therefore needs to consider not only whether a user authenticated successfully, but where the authentication occurred, what device was involved, how the session was established and what happened afterwards. Strong phishing-resistant authentication such as passkeys/FIDO2, combined with Conditional Access, device compliance and continuous identity monitoring, provides a stronger defence against token-based attacks than relying on MFA alone.
Expert in the Cloud – The Future Is Now.
Leave a Reply