Topic · Threats
Adversary-in-the-middle phishing
Adversary-in-the-middle phishing intercepts an authentication session through a deceptive proxy to capture credentials or session material.
How it works
An attacker operates a lookalike login flow that relays traffic to the real service and records usable session artifacts.
What can go wrong
Traditional password-only defenses and some challenge types may not stop an already stolen session.
What to check or do
Prioritize phishing-resistant authentication and inspect suspicious session tokens and sign-in telemetry.
Practical scenario
An employee is redirected to a convincing reverse-proxy login page. They complete password and MFA challenges, but the attacker retains a reusable session artifact and accesses the genuine cloud mailbox afterward.
Verification checklist
- Confirm the user-visible login hostname and analyze recent sign-in events.
- Revoke sessions and refresh grants while changing compromised credentials.
- Inspect browser, endpoint and mailbox telemetry for persistence.
- Deploy phishing-resistant authentication and conditional session controls.
Put this into practice
Run a focused check, then explore protection if your domain needs it.