Replay Attack
Pronunciation: ree-PLAY uh-TAK
Definition
Replay Attack is an attack or weakness pattern that resubmits a previously valid message or transaction so a system performs an authorized action again unintentionally. Defenses against Replay Attack combine secure design, least privilege, validation, monitoring, rate or value limits, and tested containment and recovery procedures.
Overview
Meaning and scope
Replay Attack is an attack or weakness pattern that resubmits a previously valid message or transaction so a system performs an authorized action again unintentionally. Defenses against Replay Attack combine secure design, least privilege, validation, monitoring, rate or value limits, and tested containment and recovery procedures.
How it works
Replay attacks exploit systems that verify authenticity but do not adequately verify freshness, uniqueness, or context. An attacker captures a valid signed request, authentication exchange, payment instruction, or blockchain transaction and presents it again. A signature can remain mathematically valid during replay because the original signer genuinely authorized the captured data. Exposure increases when messages lack nonces, timestamps, sequence numbers, expiration, chain identifiers, session binding, or records of prior use. Protocols should bind authorization to a unique domain and intended action, reject used identifiers, enforce suitable time windows, and store replay state reliably. Cross-chain, cross-contract, cross-environment, and restored-backup scenarios need explicit separation because identical credentials may exist in several contexts.
Practical payment example
An API receives the same signed withdrawal instruction twice. The system checks its unique request ID and rejects duplicate execution while preserving the original result.
Operational checks
A replay attack reuses a previously valid signed message or transaction in a context where it should not authorize a second action. Domain separation, nonces and chain identifiers can limit it. Authenticity does not guarantee freshness; replay resistance requires unique context, bounded validity, and reliable detection of previously accepted messages. Assessment of Replay Attack should trace an attack or weakness pattern that resubmits a previously valid message or transaction so a system performs an authorized action again unintentionally from prerequisite and entry point through observable impact on the affected service.
Distinctions and limits
Replay attacks are not ordinary retries when the operation is deliberately protected by idempotency. Blockchain replay protections and application-layer request controls solve different scopes. Retesting for Replay Attack should reproduce the Replay attack path involving attack, examine adjacent paths, and verify the conditions for safely returning the affected service to normal operation.
Related reading
Related reading: authentication, payment instruction.
Example
An API receives the same signed withdrawal instruction twice. The system checks its unique request ID and rejects duplicate execution while preserving the original result.
Comparison
Replay attacks are not ordinary retries when the operation is deliberately protected by idempotency. Blockchain replay protections and application-layer request controls solve different scopes.
Key Takeaway
Bind every sensitive signature to its intended context and one-time execution semantics.
Sources
- NIST Documentation: Cyberframework — NIST (2026-07-30)
- FATF Documentation: Virtual Assets — FATF (2026-07-30)