Zombie Card Attack Can Revive Expired Visa Cards for Contactless Payments
Researchers at UMass Amherst demonstrated the "Zombie Card" attack, which revives expired Visa contactless cards for real in-store purchases by rewriting the NFC-exchanged expiration date via a man-in-the-middle relay, without breaking any card cryptography. The attack exploits a protocol design flaw in Visa's Kernel 3: the Application Expiration Date (TLV tag 5F24) is not cryptographically bound to the Track 2 Equivalent Data (tag 57), and the fDDA signature explicitly excludes 5F24 from verifi
Analysis
TL;DR
- Researchers at UMass Amherst demonstrated the "Zombie Card" attack, which revives expired Visa contactless cards for real in-store purchases by rewriting the NFC-exchanged expiration date via a man-in-the-middle relay, without breaking any card cryptography.
- The attack exploits a protocol design flaw in Visa's Kernel 3: the Application Expiration Date (TLV tag 5F24) is not cryptographically bound to the Track 2 Equivalent Data (tag 57), and the fDDA signature explicitly excludes 5F24 from verification.
- Field tests across five major US banks showed one issuer (Bank A) approved revived transactions up to $500, while another (Bank B) declined them; two other EMV kernels (Mastercard, Amex, Discover) were found to be resistant due to stricter consistency checks or stronger authentication bindings.
- The attack requires physical possession or sustained NFC proximity to the expired card, a MitM relay (demonstrated with two Android phones), and an account that remains open under the same PAN—conditions common when issuers send replacement cards.
- No CVE has been assigned, no exploitation has been reported, and no vendor or network advisory or mitigation guidance had been published as of August 20, 2026; the optional EMV Relay Resistance Protocol was absent from all tested terminals.
Why It Matters
This research exposes a real-world cryptographic design gap in one of the world's most widely deployed payment protocols, showing that expired cards can be operationally resurrected for fraud without any key compromise. For AI and security practitioners, it highlights how protocol-level assumptions—such as which fields are included in authentication signatures—can create exploitable inconsistencies that persist across billions of deployed terminals and cards. The findings also underscore the critical importance of responsible disclosure timelines and the current absence of industry-wide mitigation guidance.
Technical Details
- Attack vector: A man-in-the-middle relay intercepts NFC communication between an expired Visa contactless card and a POS terminal, rewriting TLV tag 5F24 (Application Expiration Date) to any future date while leaving tag 57 (Track 2 Equivalent Data) untouched, so the issuer-verified cryptogram remains valid.
- Protocol flaw in Visa Kernel 3: The two expiry representations are consumed by different parties—the terminal checks 5F24 for local processing restrictions, while the issuer derives expiry from tag 57 in the online authorization. Visa Kernel 3 does not require these two values to be consistently bound, and the fDDA signature excludes 5F24 entirely. Additionally, Terminal Verification Results are set to all zeros, preventing the issuer from detecting whether the terminal's expiry check failed.
- EMV kernel comparison: Mastercard Kernel 2 performs a consistency check between the two expiry representations during READ RECORD parsing and declines mismatches. American Express Kernel 4 binds the expiration date into static data covered by offline data authentication, causing a hash mismatch. Discover Kernel 6 uses Combined Dynamic Data Authentication, which binds card-returned TLV objects into the verified transaction hash, also causing declines.
- Implementation and performance: The relay was built using two NFC-capable Android phones running custom card-emulator and POS-emulator software over Wi-Fi, tested against SumUp Solo and SumUp Plus readers. Each APDU round trip added ~20 ms for relay and ~50 ms with modification, averaging ~415 ms per transaction against the EMV 500 ms per-command limit. None of the tested terminals implemented the optional EMV Relay Resistance Protocol (RRP).
- Field evaluation: Tests spanned five major US banks. Bank A approved revived transactions ($1, $100, $500, plus small retail and grocery purchases). Bank B accepted the modified expiry at the terminal level but the issuer declined all attempts. A separate finding revealed that one card automatically replaced for having under three months of validity remaining continued to work alongside its replacement on Kernel 6, even though the expiry edit itself failed there.
Industry Insight
- Payment networks and terminal vendors should prioritize updating EMV kernel specifications to cryptographically bind all expiry representations and include them in dynamic authentication signatures, closing the inconsistency that Visa Kernel 3 currently permits.
- Issuers should implement independent expiry validation at the authorization layer rather than relying solely on terminal-reported results, especially since Kernel 3's zeroed Terminal Verification Results obscure whether local expiry checks passed or failed.
- The absence of the optional Relay Resistance Protocol across all tested terminals is a systemic vulnerability; mandating RRP adoption would not only mitigate relay-based expiry rewriting but also address a broader class of NFC man-in-the-middle attacks on contactless payments.
Disclaimer: The above content is generated by AI and is for reference only.