The XRP Ledger rolled out an urgent software update on September 25 after researchers uncovered a vulnerability that, in theory, could have generated 18.5 trillion XRP—far exceeding the network’s capped supply of 100 billion.
Timeline of the discovery and response
The flaw was first identified on September 22. Developers confirmed the issue the same day and merged a corrective commit on September 23. The patch was packaged in xrpld version 3.4.1 and made publicly available two days later, allowing node operators to apply it immediately.
Nature of the vulnerability
The bug lay in the payment engine’s handling of certain aggregation code, creating an overflow condition that would let attackers mint unlimited XRP. A proof-of-concept demonstrated how specially priced offers could disperse the newly created tokens across many accounts, each remaining under the ledger’s per-account balance limit. The theoretical value of the illicitly created XRP was estimated at roughly $94 billion.
Governance shortcut and its implications
XRPL normally requires validators to vote on protocol changes over several weeks before activation, ensuring a coordinated transition. In this case, developers chose to bypass that amendment route to prevent the exploit details from becoming public and giving malicious actors a window to act. The trade-off was a brief period during which nodes running different software versions might interpret the same transaction inconsistently.
Adoption speed and remaining risk
According to monitoring firm Veria, more than 80% of validators had upgraded to the new code by the day of release, sharply reducing the window of vulnerability. Nodes that delayed updating could have processed a malicious transaction differently from upgraded peers, but no evidence of such activity has surfaced on the public ledger.
Legacy code and future safeguards
The problematic aggregation routine dated back to 2015, while an invariant designed to prevent XRP over-creation had been in place since 2017. Their long-standing presence highlights the challenges of maintaining legacy blockchain code. The incident also sparked discussion about the role of AI-assisted tools in both uncovering hidden bugs and potentially easing attackers’ discovery of weaknesses.
Why it matters
The emergency patch demonstrates how decentralized networks must balance rapid security responses with transparent, validator-driven governance. While the swift upgrade averted a massive theoretical supply shock, the episode underscores the need for continuous code audits and clearer emergency procedures to protect ecosystem stability.
Why it matters
A flaw capable of inflating XRP supply by orders of magnitude threatened market confidence and the ledger’s economic model. By fixing the issue quickly and achieving rapid validator support, the XRPL community averted a potential crisis, but the event raises lasting questions about how decentralized platforms handle urgent security threats without compromising their governance principles.
