Deconstructing the Reddit Breach and the AiTM Phishing Threat
SMS-based authentication failed during the 2023 Reddit breach, providing a false sense of security against a reverse-proxy attack designed to harvest live session tokens.

We trained users for a decade to look for the padlock in the address bar. Then we told them to turn on two-factor authentication. Both directives were technically sound and operationally insufficient. The reality of modern identity infrastructure is that if an attacker can sit between the user and the identity provider, the authentication method ceases to matter. The credential is submitted, the multifactor challenge is passed, and the resulting session token is quietly captured in transit.
The reddit phishing attack 2023 perfectly illustrates this structural vulnerability. It was a masterclass in adversary-in-the-middle phishing, demonstrating exactly how a highly targeted lure combined with a reverse-proxy framework can bypass SMS-based multifactor authentication to unravel a corporate SaaS environment. By dissecting this incident, security engineering teams can understand the exact mechanics of modern token theft and architect identity boundaries that actually withstand proxy-based interception.
The Anatomy of the Intranet Lure
The initial access vector relied on highly targeted spear-phishing emails sent directly to Reddit employees. The adversaries did not cast a wide net with generic password reset lures. Instead, they adopted the persona of internal IT and directed employees to a fake intranet gateway. The emails were crafted to create a plausible administrative urgency, a tactic mapped to MITRE ATT&CK technique T1566.002 for Spearphishing Link.
Evading Email Security Controls
To bypass secure email gateways, the attackers likely utilized freshly registered lookalike domains configured with flawless email authentication. A newly registered domain passing SPF checks under RFC 7208, holding a valid DKIM signature under RFC 6376, and aligned with a strict DMARC reject policy will often sail past basic reputation filters. The content of the email instructed users to log into a portal that visually mirrored Reddit's actual internal identity provider landing page.
This phase relies entirely on context manipulation. If an employee expects regular communications regarding internal gateway updates or mandatory access portal migrations, a well-formatted email originating from a technically validated, albeit deceptive, domain is highly effective. The user clicks the link, initiating a TLS connection not to the legitimate enterprise identity provider, but to an adversary-controlled server waiting to mediate the transaction.
Reverse Proxies and the SMS MFA Bypass
The core of this compromise was an Adversary-in-the-Middle framework, likely a tool similar to Evilginx2 or Modlishka. Unlike traditional phishing pages that present a static HTML form to harvest a username and password, an AiTM framework acts as a real-time reverse proxy. When the Reddit employee navigated to the malicious link, the attacker's server fetched the legitimate Okta or Azure AD login page and served it to the victim.
Every keystroke, every password submission, and every multifactor authentication code entered by the user was passed through the attacker's server to the real identity provider. The victim received an SMS code on their phone, typed it into the phishing page, and the proxy forwarded that exact valid code to the authentic IdP. The IdP validated the code and responded with a successful authentication payload, which critically included the persistent session cookie.
The flaw in SMS and TOTP authentication is that they rely on the user to assert the context of the login. The user cannot cryptographically distinguish between the legitimate relying party and a proxy forwarding their secrets. — Security Architecture Principle
Session Cookie Interception
As the identity provider returned the Set-Cookie HTTP headers to establish the authenticated session, the AiTM proxy intercepted them. The framework extracts and logs these session tokens before passing the traffic back to the victim. Often, the framework will then redirect the victim to the actual, legitimate corporate application to minimize suspicion. The attacker now possesses a live, authenticated session cookie that has already cleared the MFA challenge. They simply import this cookie into their own browser and access the SaaS environment as the compromised user.
Lateral Movement Across the SaaS Plane
Once the attacker injected the stolen session cookie into their browser, the identity provider viewed them as an authenticated internal employee. The initial breach was limited to a single set of user credentials, but in a flat SaaS architecture, a single compromised identity often holds the keys to the kingdom. The adversary did not need to exploit a zero-day vulnerability or drop a remote access trojan on a corporate endpoint. They simply clicked through the internal web portals.
The pivot moved rapidly from the central identity portal into downstream business applications. The attacker accessed internal wikis, administrative dashboards, and crucially, the internal code repositories. This represents a fundamental failure in zero-trust architecture, where authorization is presumed based solely on the presence of a valid bearer token, regardless of the network origin or device posture associated with the request.
Dwell time in SaaS environments can be notoriously difficult to detect if security operations centers are solely monitoring endpoint telemetry. Unless identity access logs are being aggressively parsed for anomalous geographic logins, impossible travel scenarios, or sudden spikes in repository cloning activity, an attacker navigating via a hijacked session cookie looks identical to an employee doing their daily work.
Extortion and the Blast Radius
The objective of the lateral movement was data exfiltration. The adversaries successfully downloaded hundreds of gigabytes of proprietary data, including internal company documents, contracts, and a significant portion of Reddit's internal source code. While primary production systems holding user passwords and financial data were not breached, the exposure of backend source code provides threat actors with blueprints to search for hardcoded secrets, API vulnerabilities, or logic flaws for future campaigns.
Months after the initial intrusion, the ransomware affiliate group ALPHV claimed possession of the stolen archive. In a highly public extortion attempt, the group demanded a multimillion-dollar payout and the rollback of controversial API pricing changes Reddit had recently implemented. This incident highlights how data theft extortion has decoupled entirely from the deployment of encryption malware. The leverage is the data itself, and the access vector was a simple, intercepted web session.
Architecting Phishing-Resistant Identity
Defending against AiTM frameworks requires abandoning shared secrets and relying on cryptographic proofs bound to the domain. The explicit technical control to defeat this attack chain is the mandatory enforcement of FIDO2 WebAuthn authentication. Unlike SMS codes or authenticator app push notifications, WebAuthn relies on public key cryptography where the user's device holds the private key.
The Cryptographic Domain Check
When a FIDO2 challenge is initiated, the browser automatically verifies the Relying Party ID against the domain in the address bar. If an employee is tricked into visiting a lookalike proxy domain, the browser will refuse to sign the authentication challenge because the origin domain does not match the registered domain of the identity provider. The AiTM proxy cannot forward a valid response because the cryptographic signature fails at the browser level. The attack is mathematically neutralized before a session token can ever be generated.
Furthermore, organizations must implement device-bound session policies. Session cookies should be continuously evaluated against endpoint health and device compliance states. If a valid session cookie is suddenly presented from an unregistered, unmanaged device operating from an anomalous IP space, the identity provider must instantly revoke the session and force a re-authentication flow. Enforcing conditional access policies that mandate managed devices blocks an attacker from importing a stolen cookie into their own browser.
The takeaway
The compromise of internal developer environments via session hijacking is the defining access vector of the modern cloud era. As long as enterprises rely on authenticators that ask users to manually verify context via SMS or six-digit codes, adversaries will continue to build proxies that sit quietly in the middle of that conversation.
Closing this attack path requires a hard pivot to hardware-backed, phishing-resistant authentication combined with continuous token evaluation. If you are investigating suspicious SaaS access patterns or hunting for the initial email vectors that facilitate these proxy campaigns, running your message headers and domain telemetry through a platform like MailSleuth.AI can isolate the exact infrastructure adversaries are using to bypass your perimeter. Do not wait for source code to appear on an extortion blog to realize your session tokens are walking out the door.
We dissect phishing campaigns and email infrastructure so you don't have to.


