What is Adversary-in-the-Middle (AiTM)?
Traditional phishing campaigns rely on static fake login pages to harvest passwords. However, if MFA is enabled, the stolen password alone is useless; attackers get stuck at the second lock. To bypass this, attackers use Reverse Proxy / Adversary-in-the-Middle (AiTM) phishing. Instead of showing a static copy, the attacker sets up a live reverse proxy server between you and the real website. When you click the phishing link, the proxy connects to the real Microsoft, Google, or Okta on your behalf, fetches the actual login page, and displays it to you pixel-by-pixel in real-time. Furthermore, advanced campaigns often utilize Browser-in-the-Browser (BitB) techniques to simulate a fake address bar within the page frame, meaning no fake address is actually visible in the browser; the user sees the completely legitimate URL (e.g., https://login.microsoftonline.com) and cannot detect any anomalies.
How the Attack Works
Since the victim interacts with the actual login portal, everything looks authentic:
- The victim enters their real password, and the proxy relays it to the legitimate server (e.g., Microsoft).
- The real server triggers an MFA challenge (SMS, OTP, or Push), and the proxy relays it back to the victim.
- The victim approves the MFA prompt. The legitimate server then generates an authorized session cookie to log the user in.
- The reverse proxy intercepts and captures the session cookie before it reaches the victim's browser.
- Concurrent Access: As a result, while the user successfully logs into their legitimate account, the attacker simultaneously logs in at the exact same time using the captured session cookie. The victim continues working in their session completely unaware that a concurrent user is accessing their account in parallel.
Tools of the Trade: Open Source vs. Commercial Phishing Kits
The barrier to entry for executing AiTM attacks has dropped to near zero due to the availability of both free open-source tools and highly polished commercial Phishing-as-a-Service (PaaS) platforms:
- Open-Source Frameworks: Tools like
Evilginx, Modlishka, and Muraena are completely free, open-source, and readily accessible on GitHub. They ship with pre-configured templates (phishlets) for major corporate portals like Microsoft 365, Google Workspace, Okta, and consumer platforms like PayPal.
- Commercial Kits (PaaS): Advanced platforms like
EvilProxy, Tycoon 2FA, Mamba 2FA, and Starkiller are sold on Telegram as subscription services. These subscription models provide bulletproof hosting, automated IP rotation, and continuous updates to bypass Microsoft's detection algorithms.
The Rapid Rise of Reverse Proxy Phishing
Statistically, reverse proxy phishing is the fastest-growing attack vector in email security today:
- Exponential Growth: Between September 2025 and March 2026, reverse proxy phishing campaigns increased by 139%. Today, nearly 1 in 4 (25%) phishing links actively carry a reverse proxy payload.
- Widespread Impact: Just in the past year, 18 major US universities were compromised in coordinated AiTM campaigns. Simultaneously, active Microsoft 365 credential-harvesting campaigns are targeting thousands of organizations worldwide, from SMEs to Fortune 500 enterprises.
Adversarial Evasion and Traffic Distribution Systems (TDS)
To avoid detection by Threat Intelligence (CTI) crawlers, modern phishing proxies implement advanced evasion techniques:
- Traffic Distribution (TDS): They filter incoming traffic based on IP reputation, hosting provider, geolocations, and referrer headers.
- JA3/JA4 TLS Fingerprinting: They verify the TLS handshakes of incoming requests. Headless browsers or HTTP clients are detected and blocked.
- Cloaking: If a security bot is detected, the proxy shows a
404 Not Found or redirects to a benign page, masking the threat from automated crawlers.
Enterprise Mitigation and SOC Strategies
Traditional password security and basic MFA methods fail against AiTM. Modern organizations must adopt a defense-in-depth approach:
1. Mandate FIDO2 and Passkeys
FIDO2 / WebAuthn standard binds the authentication credentials cryptographically to the exact domain name (origin). If the browser domain is spoofed, the security key refuses to sign the challenge, stopping the proxy attack instantly.
2. Device Trust and Conditional Access
Configure access rules to require managed and compliant corporate devices. Even if an attacker steals the session cookie, they cannot use it on an unmanaged device, rendering the stolen cookie useless.
3. Token Binding and Short Session Lifetimes
Reduce session lifetimes to shrink the window of opportunity for stolen cookies. Where supported, enforce Token Binding to lock the session cookie to the cryptographic hardware identifier of the specific device.
4. SOC Behavioral Hunting
SOC teams must look beyond failed logins and start hunting for anomalous post-MFA actions:
- Impossible Travel: Accessing the same session cookie from geographically impossible locations within short timeframes.
- Post-Authentication Changes: Instant creation of inbox forwarding rules, new OAuth application consent, or sudden mass file downloads from SharePoint.
How Tetik.NET Protects Your Brand
Tetik.NET bypasses adversarial JA3/JA4 and TDS cloaking by executing scans through a distributed network of residential proxies and browser Extension Nodes. With our advanced Anti-Phishing framework, we perfectly match real user browser signatures, bypass attacker evasion filters, and force the phishing proxy to reveal its true malicious payload. Once detected, automated abuse reports and Google Safe Browsing / SmartScreen blocks are triggered instantly.
Exposing attackers' cloaking and evasion techniques to render threats visible is the baseline of proactive brand protection.