Threat actors are increasingly leveraging adversary-in-the-middle (AitM) phishing techniques to compromise Microsoft 365 accounts. In a recent incident, attackers used a phishing email with a malicious link that mimicked the Microsoft login page, capturing both credentials and session cookies to bypass multi-factor authentication (MFA). The attackers expanded their access through password spraying, brute force attacks, and the use of VPNs and residential proxies to evade detection. Persistence was achieved by manipulating inbox rules and abusing OAuth permissions via legitimate email clients, allowing continued access to compromised accounts.
Traditional detection methods, such as URL reputation and static fingerprinting, are proving ineffective against these sophisticated AitM phishing kits, which proxy the real Microsoft authentication flow and associated assets. In response, security researchers have developed new defensive measures, including browser extensions that detect AitM attacks at the point of interaction by monitoring for unexpected HTTP referers and injecting visible warnings. However, as attackers adapt and proxy more elements of the authentication process, even these advanced defenses face challenges, highlighting the need for continuous innovation in anti-phishing strategies.

Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
8 events from the most recent confirmed update back to the earliest known activity.
The analysis disclosed that the attacker used VPNs, residential proxies, and cloud services to blend into legitimate traffic and avoid detection. It also identified monitoring opportunities such as unusual authentication patterns, inbox rule changes, OAuth grants, and anomalous Microsoft Graph API activity.
After establishing persistence, the attacker moved laterally by using compromised accounts for internal phishing and by abusing Dropbox to distribute malicious PDFs. The campaign leveraged trusted internal channels and cloud services to deepen the compromise.
The attacker maintained access by manipulating inbox rules and abusing OAuth, including registering a legitimate eM Client application with high-risk Microsoft Graph API permissions. This created durable access paths beyond the original stolen session.
In the same BEC campaign, the attacker used password spraying, brute force, and legacy authentication protocols to broaden access to additional accounts and services. These steps marked an escalation from initial credential theft to wider compromise.
A separately analyzed business email compromise campaign started with an adversary-in-the-middle phishing attack that captured credentials and session tokens, enabling the attacker to bypass multi-factor authentication. The intrusion then expanded beyond the initial compromise into broader account abuse.
Eye Security reported that M365 AitM Block achieved a high detection rate against contemporary phishing kits, including kits using obfuscation and anti-debugging techniques. This provided new technical detail on a defensive approach for identifying modern M365 phishing attacks.
Eye Security developed M365 AitM Block for Chrome and Edge to detect Microsoft 365 AitM phishing during the login process by monitoring DOM elements and layout properties rather than relying on static page analysis. The extension was designed to work fully offline and warn users when suspicious login flows are detected.
Eye Security documented that adversary-in-the-middle phishing against Microsoft 365 had evolved to use real-time proxying of authentication flows, allowing attackers to steal credentials and session tokens while evading traditional URL- and reputation-based detection. The research described these attacks as increasingly sophisticated and effective against modern login protections.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.