What Is Evilginx and Reverse-Proxy Phishing? How MFA Bypass Works
Reverse-proxy phishing (widely known through red-team tools such as Evilginx) is an Adversary-in-the-Middle (AitM) attack where a phishing domain acts as a live relay between your browser and the real Microsoft, Google, or workspace login server. Because it forwards your password and 6-digit MFA code in real time, the real server issues a logged-in session cookie straight through the attacker's proxy—which FIDO2 passkeys prevent.
Many people assume that turning on Two-Factor Authentication (2FA)—like SMS codes or 6-digit authenticator numbers—makes clicking a phishing link harmless. While any MFA is vastly better than passwords alone against leaked-password attacks, reverse-proxy phishing changed the rules for live phishing links. Understanding how the relay works in plain English shows why checking the domain—and upgrading to passkeys—matters so much.
Pixel-accurate live login flow (even displays your real company branding banner after typing your email!)
Browser is connected to login.microsoftonline.security-token-gateway[.]net -> Proxy relays traffic to real login.microsoftonline.com and copies Set-Cookie session token
- Because the proxy fetches content live from the real provider, your custom corporate background logo and real MFA prompt appear dynamically.
- Only the browser address bar betrays the attack: the root domain before the first / is NOT microsoftonline.com or google.com.
- A FIDO2 passkey or hardware security key refuses to sign the login challenge because the origin domain does not match.
Classic Static Phishing vs. Reverse-Proxy (AitM) Phishing
In a traditional phishing attack, scammers built a static fake HTML copy of a login page. You typed your email and password, the fake site saved them in a text file, and if your account required a 6-digit authenticator code that expired every 30 seconds, the attacker often could not use your password later.
A reverse proxy flips that model. Originally created by security researcher Kuba Gretzky as Evilginx for authorized penetration testing so organizations could test their defenses, reverse-proxy kits do not host fake HTML pages at all. Instead, the attacker's server acts like a transparent glass window sitting between you and the real login website.
Why Passkeys and FIDO2 Security Keys Defeat Reverse Proxies Completely
Why can a reverse proxy relay a 6-digit code or push tap, yet fail completely against a passkey (Face ID / Touch ID / Windows Hello passkey or a YubiKey)? Because a 6-digit number has no idea what website your browser is currently looking at—you read the digits with your eyes and type them onto any domain.
FIDO2 / WebAuthn passkeys work cryptographically inside the browser itself. Before signing a login challenge, your browser hands the passkey the exact origin domain from the address bar (for example, login-portal-verify[.]com). Because your passkey was registered exclusively to microsoft.com or google.com, it refuses to sign—and even if a proxy tried to alter the challenge, the cryptographic signature would fail verification on the real server.
Practical Protections for Individuals and Workplace Teams
Even before every service you use supports passkeys, four habits shut down reverse-proxy attacks reliably:
- Switch primary email & cloud accounts to passkeys: Google, Microsoft, Apple, GitHub, and major password managers all support phishing-resistant passkeys today.
- Check the root domain even if you see your company logo: Never treat your organization's custom login wallpaper as proof of authenticity—a reverse proxy relays that wallpaper live from the real server. Only the domain before the first / tells the truth.
- Let your password manager check the URL first: Your password manager will not autofill on the proxy's fake domain.
- If you clicked, revoke active sessions too—don't just change your password: Because the attacker stole an already-authenticated session cookie, make sure to click 'Sign out of all sessions / devices' in your security settings right alongside resetting your password.
Chapter 3 · Malicious Links & Fake Websites
Walk through an interactive visual simulation of credential + session-cookie relay and FIDO2 origin binding inside NoBait Threat Academy.
Frequently Asked Questions
Does Evilginx mean I should turn off Two-Factor Authentication?
Never turn off MFA! Standard authenticator apps still block automated password-stuffing and data-breach replay attacks. To block live reverse-proxy phishing as well, add a phishing-resistant passkey or hardware security key (FIDO2 / WebAuthn) where supported and always verify the login domain.
Why did a fake phishing page show my real company logo after I typed my email?
Because a reverse proxy relays your email address to Microsoft or your SSO provider in real time and forwards the real branding response back to your screen. Always verify the domain name in the browser address bar.
If a session cookie was stolen, is changing my password enough?
Changing your password is essential, and many cloud providers automatically invalidate tokens on password reset, but you should also explicitly click 'Sign out everywhere' or 'Revoke all sessions' (and check inbox forwarding rules) to terminate any active session cookies immediately.
