Live briefing · Decrypt
XRP Ledger’s Payment Engine Had a Counterfeiting Bug Hiding Since 2015
What Decrypt reports, why it matters and what remains unconfirmed.
CryptoBy Decrypt Agent at Decrypt
The story in one view
- Reported by
- Decrypt
- Coverage lens
- Security and resilience
- Published
- Evidence status
- Cross-source reports linked
What Decrypt reports
An integer overflow in the payment engine, dormant since 2015, could have let an attacker mint spendable XRP beyond the token’s total supply.
The immediate significance
The report identifies a security development, but the available information does not provide enough matched evidence for a more specific impact judgment. That assessment remains open.
CoinDesk has also published a related report, providing another attributed account to compare without treating repetition as proof.
What remains unknown
- No matched primary document independently supporting the central claim is linked to this page.
Live market check
The named assets, right now
Spot quotes from Kraken, checked .
Developing Across Sources
How the story developed
CoinDesk and Decrypt are reporting related developments. Reports are shown in publication order; separate coverage is not independent confirmation.
CoinDesk Why a bug that could have threatened XRP's 100 billion supply cap stayed hidden for years
The XRP Ledger Foundation said normal parameters never triggered the bug that could have broken XRP's supply cap, which is why it was undetected for years.
DecryptCurrent briefing XRP Ledger’s Payment Engine Had a Counterfeiting Bug Hiding Since 2015
An integer overflow in the payment engine, dormant since 2015, could have let an attacker mint spendable XRP beyond the token’s total supply.
Related Articles And Podcast
Further reporting and analysis on this story.
Podcast11 min
Daily Crypto Deep Dive: The XRP Bug That Could Have Created 18 TRILLION XRP – How Close Was Disaster?
The XRP Bug That Could Have Destroyed Its 100 Billion Supply Cap
Read the notes and play the episode