A new report from Barracuda highlights the growing sophistication of email-based threats, singling out a Phishing-as-a-Service (PhaaS) platform known as Tycoon 2FA. This platform enables even low-skilled attackers to conduct advanced adversary-in-the-middle (AiTM) attacks that can bypass traditional multi-factor authentication (MFA). The attack works by proxying the real Microsoft login page to the victim. When the user enters their credentials and approves the MFA prompt, the Tycoon 2FA kit intercepts the session cookie generated after the successful login. This cookie is then used by the attacker to access the victim's Microsoft 365 account without needing the password or MFA device. This technique renders many common MFA methods, such as push notifications and SMS codes, ineffective, underscoring the urgent need for phishing-resistant MFA.
The Tycoon 2FA attack is a prime example of an adversary-in-the-middle (AiTM) phishing campaign. The process is seamless for the victim, making it highly effective:
.ics file) that, when accepted, contains the link to the phishing site. This helps bypass some email security filters.This attack methodology maps to several MITRE ATT&CK techniques:
T1566.002 - Spearphishing Link: The initial email vector.T1556.002 - Adversary-in-the-Middle: The core of the attack, using a reverse proxy to intercept the authentication flow.T1539 - Steal Web Session Cookie: The ultimate goal of the phishing attack is to steal the session token, not the credentials themselves.The rise of PhaaS platforms like Tycoon 2FA and EvilTokens democratizes this advanced attack. These kits provide the infrastructure (reverse proxy, templates, etc.) and sell access, allowing non-technical criminals to bypass MFA at scale.
This attack proves that not all MFA is created equal. Any MFA method that can be phished by an AiTM proxy (SMS, push notifications, one-time passwords) is vulnerable. Only phishing-resistant methods like FIDO2 provide robust protection.
The impact of a successful Tycoon 2FA attack is a full compromise of a user's Microsoft 365 account. This can lead to:
No specific IOCs such as phishing domains or IP addresses were provided in the source articles.
Detecting AiTM phishing requires looking for subtle clues in URLs and login behavior:
login.microsoftonline.com. It will be a different domain, even if the page content looks perfect..ics calendar invites in phishing emailsDetection relies on a combination of technical controls and user awareness.
The most effective mitigation is to move to phishing-resistant MFA.
microsoft.com, live.com, or microsoftonline.com.Implementing phishing-resistant MFA, such as FIDO2, is the most effective mitigation against AiTM attacks.
Mapped D3FEND Techniques:
Training users to verify the domain in the URL bar before entering credentials is a critical, though not foolproof, defense.
Using email security gateways with advanced URL analysis can block the initial phishing link before it reaches the user.
Mapped D3FEND Techniques:
The definitive countermeasure against AiTM phishing attacks like Tycoon 2FA is to upgrade from phishable MFA to phishing-resistant MFA. Organizations must prioritize the deployment of FIDO2-based authentication methods, such as Windows Hello for Business, platform authenticators (like Touch ID), or FIDO2 security keys (e.g., YubiKeys). These methods create a cryptographic binding between the user's authentication credential, the device, and the origin domain (login.microsoftonline.com). When the Tycoon 2FA proxy presents the login challenge from its own malicious domain, the FIDO2 protocol will detect the origin mismatch and refuse to complete the authentication. This technical control completely breaks the AiTM attack chain and is the only way to reliably protect against session token theft.
To detect the use of stolen session tokens, organizations should leverage Microsoft Entra ID Protection and Conditional Access policies. Configure Identity Protection to flag and block risky sign-ins, particularly those exhibiting 'impossible travel' (e.g., a user logs in from New York, and five minutes later the stolen session token is used from an IP in Eastern Europe). Furthermore, create Conditional Access policies that enforce location-based controls (e.g., blocking all logins from high-risk countries) and require access only from compliant or hybrid-joined devices. An attacker using a stolen token from their own machine will not meet the device compliance requirement, and their session will be blocked. This provides a powerful detective and preventative layer that can stop a compromised session from being used.
While technical controls are paramount, strengthening the human firewall remains important. Organizations must conduct continuous security awareness training focused on modern phishing threats. This training should specifically educate users on how to spot AiTM attacks by always verifying the domain name in the browser's address bar before entering credentials or approving an MFA prompt. Users must be taught that the page content can be perfectly cloned, but the URL cannot be spoofed. They should be trained to recognize that any Microsoft login prompt not on an official Microsoft domain (microsoft.com, microsoftonline.com, etc.) is malicious. This should be combined with phishing simulation exercises that mimic AiTM attacks to test and reinforce this critical user behavior.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.