XRP Ledger patches exploit creating extra XRP

TLDR

XRP Ledger developers have patched a critical decade-old bug that could have created new spendable XRP beyond the fixed 100 billion supply.

1. A payment-engine integer overflow in XRPLs built-in DEX could have minted unlimited XRP, but it is now fixed in server version 3.4.1.
2. RippleX reports no evidence the exploit was ever used on public networks, so the circulating supply and 100 billion cap appear intact.
3. The incident highlights protocol risk and the importance of node operators upgrading promptly and watching future security disclosures.

Deep Dive

1. What The Bug Was And How It Was Fixed

Reports describe an integer overflow in the XRP Ledger (XRPL) payment engine that settles trades on its built-in decentralized exchange. An attacker could fill hundreds of deliberately mispriced offers in a single payment so that the internal counter exceeded its numeric limit and wrapped to a small value, crediting sellers full XRP while charging the buyer almost nothing, effectively creating new XRP out of nothing beyond the 100 billion cap. This behavior is detailed in multiple disclosures and analyses including coverage by Coindesk and others that call out the possibility of billions of dollars in XRP being minted from nothing.

Researchers reported the issue through the XRPL bug bounty program on 22 September 2026, and RippleX shipped a fix in server software xrpld 3.4.1 on 25 September, adding safer arithmetic and stronger supply checks so that such overflows now fail instead of silently minting value. Over 80 percent of default trusted validators reportedly upgraded quickly to the patched version, according to technical summaries from sources like TokenPost and Yahoo Finance.

2. Was Extra XRP Actually Created

RippleX states that it has found no evidence the bug was exploited on any public XRPL network, even though researchers demonstrated the attack on isolated servers. Articles summarizing the official disclosure emphasize that all known tests of the exploit happened in controlled environments and that forensic checks have not revealed anomalous supply changes on mainnet.

However, several writeups also note that no evidence is not the same as a mathematical proof, because a sufficiently careful attacker could have tried to hide on-chain traces among normal DEX activity if they acted before the fix. Even so, the consensus of current reporting is that there is no sign the 100 billion XRP cap was actually broken on the live network.

3. Governance, Centralization And What To Watch

Because of the severity of the bug, RippleX and XRPL stakeholders reportedly bypassed the usual on-ledger amendment voting process and instead pushed the fix via a direct code upgrade that took effect as operators updated their servers. Commentators highlight this as the first time in over a decade that XRPL changed transaction-processing behavior without a full public amendment vote, in order to avoid advertising an unpatched minting vector for weeks.

This emergency path raises governance questions about centralization and how much discretion core maintainers should have, even when acting to protect the network. Going forward, the main things to watch are: how quickly nodes adopt future security releases, whether XRPL formalizes clearer emergency procedures, and whether independent audits or formal verification are expanded to catch similar issues earlier.

Conclusion

The XRP Ledger bug shows that even mature chains can carry hidden consensus-critical vulnerabilities for years, yet prompt coordinated patching can prevent them from turning into real supply crises. For XRP, current evidence suggests the 100 billion cap held in practice, but the episode is a reminder that protocol security, validator behavior, and governance design are core parts of crypto risk, not afterthoughts.