Trillion

<ul>
 <li>Developers found no evidence of exploitation on public networks.</li>
 <li>Veria estimated the flaw could create 18.45 trillion XRP per transaction.</li>
 <li>The emergency patch sparked debate over temporarily withheld source code.</li>
</ul>
An XRP Ledger security bug could have allowed attackers to create trillions of spendable tokens, developers disclosed on October 9. The flaw dated to 2015 and was patched on September 25. Developers found no evidence of public exploitation. The XRP Ledger Foundation also said on X that checks confirmed the public supply remained intact.
<h2 class="wp-block-heading" id="how-the-xrp-ledger-security-bug-bypassed-supply-checks">How the XRP Ledger security bug bypassed supply checks</h2>
Veria reported the flaw on September 22. RippleX reproduced the XRP Ledger security bug on a standalone server, confirming that newly created tokens could fund another payment.
In his<a href="https://x.com/Cayden_Liao/status/2109074675695579399" rel="noopener noreferrer nofollow"> October 10 X post</a>, Veria Labs co-founder Cayden Liao credited the discovery to Veria AI. He estimated potential creation at about 18.45 trillion XRP per transaction, over 184 times the original supply. Liao also reported a $250,000 bounty.
<figure class="wp-block-embed is-type-rich is-provider-x wp-block-embed-x">
 <div class="wp-block-embed__wrapper">
 <blockquote class="twitter-tweet">
 Our AI found a bug that let anyone mint infinite XRP, with $94B at risk. It had been hiding in one of the most audited codebases in crypto for nearly a decade, and earned us the maximum $250K bounty. Here's how it went unnoticed, and how we found it. <a href="https://t.co/m7rSD8mKS5" rel="noopener noreferrer nofollow">https://t.co/m7rSD8mKS5</a>— SuperBeetleGamer (@Cayden_Liao) <a href="https://x.com/Cayden_Liao/status/2109074675695579399?ref_src=twsrc%5Etfw" rel="noopener noreferrer nofollow">October 11, 2026</a>
 </blockquote>
 </div>
</figure>
The payment engine flaw involved integer overflow: an oversized total wrapped into a much smaller number. Sellers could receive full payments while buyers paid almost nothing. A supply safeguard repeated the arithmetic error, allowing unauthorized XRP minting.
The exploit required deliberately abnormal trading offers across hundreds of accounts. Ordinary payments could not trigger it, according to the disclosure, despite the long exposure period.
<h2 class="wp-block-heading" id="xrp-ledger-security-bug-fix-prompts-transparency-debate">XRP Ledger security bug fix prompts transparency debate</h2>
Developers shipped xrpld 3.4.1 with compiled software before releasing its source code. Justin Bons criticized the temporary withholding on X.
<figure class="wp-block-embed is-type-rich is-provider-x wp-block-embed-x">
 <div class="wp-block-embed__wrapper">
 <blockquote class="twitter-tweet">
 Selling XRP to retail as "decentralized" is straight-up fraud! XRP has been running closed-source code for the last two weeks Tomorrow, this code becomes mandatory &amp; anyone who disagrees will get kicked off the chain! A permissioned node list means validators must obey: … <a href="https://t.co/3nIcRiid8S" rel="noopener noreferrer nofollow">pic.twitter.com/3nIcRiid8S</a>— Justin Bons (@Justin_Bons) <a href="https://x.com/Justin_Bons/status/2108255639067590946?ref_src=twsrc%5Etfw" rel="noopener noreferrer nofollow">October 8, 2026</a>
 </blockquote>
 </div>
</figure>
RippleX engineer Mayukha Vadari<a href="https://x.com/msvadari/status/2108926650729550124" rel="noopener noreferrer nofollow"> replied</a> that AI could quickly expose critical fixes within public releases. Publishing the patch before protection activated would have given attackers a window to exploit the XRP Ledger security bug.
The overflow fix applied immediately when servers upgraded, bypassing the usual amendment delay. More than 80% of default UNL validators upgraded on release day.
The Foundation<a href="https://coincryptonewz.com/xrpl-expands-onchain-finance-with-amm-rwas-and-institutional-upgrades/" rel="noopener noreferrer nofollow"> said operators independently</a> chose their software and coordinated the response through community agreement. It distinguished that emergency rollout from the later amendment vote that made upgrading necessary to remain synchronized.
A separate Batch fix activated through amendments on October 9. The Foundation also pledged broader formal verification, AI adversarial testing and researcher collaboration.
<pre class="wp-block-preformatted">Disclaimer: This article is for informational purposes only and does not constitute financial advice. CoinCryptoNewz is not responsible for any losses incurred. Readers should do their own research before making financial decisions.</pre>
&lt;p&gt;The post <a rel="noopener noreferrer nofollow" href="https://coincryptonewz.com/xrp-ledger-bug-could-have-created-18-trillion-xrp-before-fix/">XRP Ledger Bug Could Have Created 18 Trillion XRP Before Fix</a> first appeared on <a rel="noopener noreferrer nofollow" href="https://coincryptonewz.com">Coin Crypto Newz</a>.&lt;/p&gt;

XRP Ledger Bug Could Have Created 18 Trillion XRP Before Fix

Table of Contents

CoinCryptoNewz

Other articles published on Oct 12, 2026

Join our free newsletter for daily crypto updates!