Join our Newsletter — 33% off our NHI Course
Home› Glossary› Threats, Abuse & Incident Response› Near-Field Communication Relay Attack
Threats, Abuse & Incident Response

Near-Field Communication Relay Attack

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

A Near-Field Communication Relay Attack is a fraud technique that forwards NFC traffic between a victim device and a legitimate reader or card. The attacker uses a relay device or software link to make the two endpoints believe they are communicating at close range, which can let a stolen credential or contactless token be used remotely.

How Near-Field Communication Relay Attacks Work

A relay attack does not crack NFC cryptography by itself. It extends the effective range of a contactless interaction by carrying messages between two devices that are actually farther apart, so the reader, token, or wallet believes it is still in a valid close-range exchange.

This matters because many NFC systems use proximity as part of the trust decision. When that assumption is broken, the attacker can preserve the appearance of a legitimate tap while shifting the real transaction elsewhere.

Why Relay Attacks Are Dangerous

The core danger is that the attacker is abusing a live authentication or transaction, not replaying an old one. If the token or credential is already valid, a relay can let an attacker use it from a distance before the user notices, especially in fast transit, building access, or payment scenarios.

Relay attacks are especially effective when systems rely on “near enough” rather than stronger presence checks. That is why guides on Bluetooth, RFID and NFC Security Guide and Digital Car Key and Keyless Entry Security Guide treat relay as a proximity-bypass problem, not just a wireless nuisance.

Where Exposure Usually Comes From

Exposure is often not obvious from a configuration screen alone. It usually comes from a mix of contactless capability, permissive reader behavior, weak user presence checks, and environments where a legitimate tap or unlock event has high value.

That is why organisations should inventory where NFC is used, identify which readers accept proximity as proof, and review whether the process can still succeed when a victim device is not physically beside the reader. The same pattern appears in mobile badges and wallet-based credentials, which is why the Mobile Access Credentials guide and the Digital Identity Wallet Fraud Risks Guide both emphasise relays as a real exposure path.

Defensive Controls and Verification

Good defenses aim to make proximity harder to fake. In practice that means using stronger device binding, transaction context checks, reader-side challenge logic where available, and ranging or distance-bounding mechanisms that are harder to relay than ordinary NFC exchange.

For physical access and vehicle use cases, this often means pairing NFC with additional assurance, such as ultra-wideband ranging, tighter revocation processes, and controls that reduce the value of a relayed tap. The most useful starting point is to align the control choice to the asset class, which is why the Physical Layer and Wireless Jamming Guide is relevant when the problem is broader than NFC alone.

Risk and Threat Considerations

Relay attacks turn a proximity assumption into an access path. The main risk is not token forgery, but fraudulent use of an otherwise legitimate credential, which can affect payments, building entry, transit passes, and vehicle unlock workflows.

Failure mechanism: The attacker keeps a live NFC session or transaction open across distance, so the reader accepts a remote party as if it were physically present.

Impact: An attacker can unlock doors, authorise transactions, or use a stolen credential without needing to extract the secret itself.

Standards & Framework Alignment

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

OWASP Non-Human Identity Top 10 addresses the attack and risk surface, while CIS Controls v8 and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
OWASP Non-Human Identity Top 10NHI-04 — Insecure AuthenticationRelay attacks abuse weak proximity-based authentication for NFC credentials.
NHI-08 — Environment IsolationRelay paths break the assumed separation between the user device and reader location.
Recommendation — Require stronger presence and binding checks for NFC-authenticated credentials. Separate trusted tap zones from untrusted relay-capable environments.
CIS Controls v8CIS-6 — Access Control ManagementRelay abuse turns access control decisions into an exposure problem.
Recommendation — Restrict contactless access paths to the minimum required business use cases.
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementNFC relay risk depends on how authenticators are issued, used, and revoked.
IA-9 — Identification and Authentication (Non-Organizational Users)Contactless credentials and mobile badges authenticate external or device-based users.
AC-17 — Remote AccessA relay effectively extends access remotely through an untrusted intermediary.
Recommendation — Manage authenticator lifecycle so relayed credentials can be revoked quickly. Apply stronger authentication controls for external and device-mediated NFC access. Treat relayed contactless sessions as remote access and tighten approval paths.

Practitioner Guidance

Why practitioners should care: NFC relay attacks are a design problem as much as a fraud problem, because the control failure often sits in the trust model rather than the token itself. If your system treats “close enough” as proof of presence, you should assume relay resistance is an explicit requirement.

What to watch for: Prioritise tap flows that unlock high-value actions, especially where the same credential can be used across multiple reader types or where a mobile device is the primary authenticator. Validate whether revocation, device binding, and distance checks actually survive real-world relay conditions.

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