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

OTP relay

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

An attack pattern where a one-time passcode is captured and reused fast enough to complete authentication before it expires. The user still appears to have authenticated normally, but the resulting session belongs to the attacker, which makes detection harder and containment more urgent.

How OTP relay works

OTP relay is a fast, interactive abuse of a one-time code flow, not a break of the code itself. The attacker intercepts the passcode in real time, forwards it to the legitimate login form, and uses the resulting authenticated session before the code expires. That makes the attack look like a normal sign-in unless the surrounding context is examined.

The technique is especially effective when the authentication journey depends on a short-lived code and the user is already conditioned to expect a prompt. Because the victim usually completes the login themselves, the attacker does not need to defeat the second factor cryptographically, they only need to win the timing and trust race. That is why this pattern often sits alongside phishing, adversary-in-the-middle activity, and support for session theft rather than classic password guessing.

Why OTP relay is dangerous

The main danger is that the authentication event still appears valid to the identity provider, the application, and often the user. Once the attacker has the live session, they may not need the OTP again, which turns a short code capture into durable account access. In practice, the attacker can move from initial credential capture to inbox access, application abuse, data theft, or privilege escalation within the authenticated session.

OTP relay is also difficult to spot because the user may not report anything unusual immediately. If the session is established from the attacker’s device, the real user may remain unaware until they see unfamiliar activity, repeated prompts, or a sign-in from a location or browser they do not recognise. The shorter the response window, the more likely the attacker can act before containment begins.

How organisations reduce exposure

Exposure usually comes down to where OTPs are still accepted as a primary protection, whether users can be pushed through a phishing flow, and how much trust is placed in the code alone. Organisations should treat internet-facing sign-in surfaces, legacy MFA paths, and help-desk recovery flows as the most likely places for relay abuse. The most resilient answer is to prefer phishing-resistant factors over reusable one-time codes, especially where the account protects sensitive data or administrative functions.

Useful guidance includes the MFA Guide for understanding where code-based methods fail, and the OTP security guide for relay-specific prevention patterns. For broader authentication hardening, the NIST digital identity guidance on phishing-resistant authenticators is the right external reference point, and the NIST SP 800-63 Digital Identity Guidelines align well with that control direction.

Detection and response after suspected relay

Detection should focus on the session, not just the login event. A successful relay often leaves normal-looking authentication telemetry but unusual follow-on behaviour, such as impossible travel, unfamiliar device fingerprints, rapid mailbox or file access, consent changes, API token creation, or new forwarding and recovery settings. If the user reports receiving an unexpected prompt or if sign-in telemetry shows a clean OTP validation followed by suspicious session activity, assume the session may already be compromised.

Containment usually means revoking active sessions, invalidating tokens where the platform supports it, and forcing a fresh authentication path that does not reuse the same weak factor. Where the compromise led to secondary secret exposure, such as API keys, recovery codes, or synced authentication material, those should also be reviewed and rotated. The MITRE ATT&CK T1598 Phishing for Information guide is useful for mapping relay to broader credential-harvesting behaviour, while MITRE ATT&CK Enterprise Matrix helps analysts connect the initial phishing stage to later access and lateral movement patterns.

Risk and Threat Considerations

OTP relay is dangerous because it weaponises legitimate authentication flow, so defenders may see a valid sign-in while the attacker is already inside the session. The risk is highest where one-time codes are the main step-up control and where session creation is immediately trusted without strong context checks.

Failure mechanism: The attacker captures the code in real time, completes the login before expiry, and inherits the authenticated session, often bypassing detection that keys only on failed logins or incorrect credentials.

Impact: The attacker can act as the user, access protected resources, and persist through token or session reuse even after the victim realises the code was stolen.

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 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-63Digital Identity GuidelinesGuides phishing-resistant authenticators and session assurance for OTP relay threats.
Recommendation — Adopt phishing-resistant authenticators to prevent intercepted one-time codes from completing authentication.
MITRE ATT&CKT1598 — Phishing for InformationCovers credential harvesting and social-engineering paths used to obtain OTPs in relay attacks.
Recommendation — Map OTP relay to T1598 and hunt for credential-harvesting activity around the login event.
NIST CSF 2.0PR.AA-05 — Protective Technology, Access ControlSupports access-control hardening against intercepted-authentication abuse.
Recommendation — Strengthen access controls to reduce reliance on reusable OTP-based sign-in alone.

Practitioner Guidance

Why practitioners should care: OTP relay is a control failure at the authentication boundary, not a user-error edge case. If your control model still treats an OTP as sufficient evidence of trust, the attacker only needs a live relay path to defeat it.

Common misunderstanding: Teams often assume that a short-lived code is safe because it expires quickly. In reality, expiry only helps if the code cannot be copied and replayed within the same login window, which is exactly what relay attacks exploit.

Practitioner takeaway: Treat any successful OTP relay as a session compromise event, then harden the sign-in path so the next factor is resistant to interception rather than merely time-limited.

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 4, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org