Join our Newsletter — 33% off our NHI Course
Threats, Abuse & Incident Response

AiTM Proxy

← Back to Glossary
By NHI Mgmt Group Updated November 5, 2026 Domain: Threats, Abuse & Incident Response

An adversary-in-the-middle proxy sits between the victim and the legitimate service to intercept credentials, tokens, or session data in real time. In phishing campaigns, it allows the attacker to capture a usable identity signal rather than only a password, which makes the compromise harder to detect and more durable.

How AiTM proxy attacks work

An AiTM proxy sits in the path between the user and the real service, relaying traffic while capturing the parts of the login flow that matter most to defenders, such as session cookies, tokens, and other usable signals. That makes it different from simple password phishing, because the attacker is trying to steal a live authenticated session as it is created.

The technique depends on convincing the victim to authenticate through the attacker-controlled relay, often with a lookalike sign-in page or redirected flow. Once the victim completes MFA, the proxy can pass the challenge to the legitimate service and still harvest the resulting session data. That is why a Man-in-the-Middle Attacks Guide is a useful companion for understanding the interception mechanics and the defences that interrupt them.

Why AiTM proxies are dangerous

AiTM proxies are dangerous because they turn a successful phishing event into immediate authenticated access. Instead of relying on a stolen password alone, the attacker may gain a session that already passed MFA, which reduces the value of many traditional phishing indicators and makes the compromise feel legitimate to the service.

This is especially problematic in environments that treat session establishment as proof of trust without checking whether the browser, network path, or token presentation looks suspicious. The attack can also bypass user awareness after the initial click, because the victim often completes the normal login ritual and sees no obvious failure.

For defenders, the practical lesson is that the identity signal being stolen is often more durable than a password. Session theft can outlive the original phishing page and may allow the attacker to move laterally, access mail, or approve additional actions before the session expires or is revoked.

Detection and exposure checks

Exposure assessment starts with understanding where interactive sign-in is used, which services accept browser-based sessions, and which users have privileged access to high-value systems. Organisations should also check whether phishing-resistant authentication, conditional access, and token-binding style protections are actually enforced on the paths that matter, not just documented in policy.

Detection is rarely about a single alert. Better signals include impossible travel, unusual device or browser fingerprints, repeated sign-in relays, suspicious consent or token issuance patterns, and sessions that appear valid but originate from an unexpected endpoint. A broader identity control baseline such as Workforce Identity Security Guide helps frame where those checks belong in workforce login, recovery, and session protection.

When reviewing exposure, teams should ask which users, applications, and authentication paths remain vulnerable to relay-based interception even if MFA is enabled. That review is strongest when paired with authoritative control guidance such as NIST SP 800-63 Digital Identity Guidelines, which is widely used to evaluate phishing-resistant authentication and authenticator strength.

Defences and recovery after compromise

The strongest defences reduce the attacker’s ability to reuse what they capture. Phishing-resistant authenticators, modern session protections, shorter-lived tokens, reauthentication for sensitive actions, and device or context checks all make proxy interception less useful. Defensive layering matters because no single control stops every relay pattern.

After a suspected AiTM compromise, organisations should assume the session, not just the password, may be exposed. That means revoking active sessions, invalidating tokens where possible, reviewing mailbox and identity activity, and checking for consent grants, forwarding rules, or privilege changes that occurred during the valid session window.

In many environments, the most valuable follow-up is not just credential reset, but a complete review of what the attacker could do with the hijacked session before it was detected. That is where NIST Privacy Framework and related identity controls can complement response thinking, because the harm often sits in what the attacker could observe, access, or persist through during the session.

Risk and Threat Considerations

AiTM proxy attacks matter because they defeat the basic assumption that a successful MFA prompt proves the user is authentic and the session is safe. The attacker is not just stealing a password, but a working identity transaction that may already carry trusted access.

Failure mechanism: The proxy relays the victim’s login in real time, captures the resulting session artefacts, and reuses them before defenders or the user realise the session has been hijacked.

Impact: The attacker can impersonate the user with a valid session, access protected systems, and extend compromise into mail, approvals, data access, or privilege escalation.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

MITRE ATT&CK addresses the attack and risk surface, while NIST SP 800-63, NIST CSF 2.0 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-63Digital Identity GuidelinesDefines phishing-resistant authentication and authenticator assurance for sign-in trust.
Recommendation — Use phishing-resistant authenticators and stronger assurance requirements for sessions exposed to relay attacks.
NIST CSF 2.0PR.AA-05 — Identity Management, Authentication, and Access ControlAiTM directly exploits authentication and access control weaknesses in interactive sign-in flows.
Recommendation — Enforce strong authentication and access controls that resist credential and session relay attacks.
MITRE ATT&CKT1557 — Adversary-in-the-MiddleAiTM is the adversary-in-the-middle technique used to intercept credentials and session data.
Recommendation — Map proxy-based phishing activity to T1557 and hunt for relay patterns in sign-in telemetry.
NIST SP 800-53 Rev 5IA-2 — Identification and Authentication (Organizational Users)Interactive workforce sign-in security depends on authenticating users before granting session access.
IA-5 — Authenticator ManagementAiTM commonly abuses authenticators, tokens, and session material that must be managed lifecycle-wise.
Recommendation — Apply IA-2 to strengthen user authentication paths that AiTM attacks try to hijack. Control authenticator issuance, protection, renewal, and revocation to limit relay abuse.

Practitioner Guidance

What to watch for: Treat AiTM as a session-security problem as much as an authentication problem. If your controls stop at password resets and basic MFA, you may still leave a live session available to the attacker after the user has already “logged in” successfully.

Governance implication: Put clear ownership around session revocation, sign-in risk review, and phishing-resistant authentication coverage, especially for privileged users and high-value applications. NIST Privacy Framework and identity guidance are most useful when they drive operational decisions, not just policy language.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 5, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org