XRP Ledger patches bug that could mint 18 trillion XRP

XRP Ledger security bug patch shown with Ripple, Bitcoin and Ethereum coins

The XRP Ledger patched a decade-old payment engine flaw that could have let an attacker create about 18.45 trillion XRP in a single transaction, more than 184 times the token’s fixed 100 billion supply, according to CoinDesk. The fix shipped in xrpld 3.4.1 on September 25, and RippleX said it found no evidence the bug was exploited on any public network. A full disclosure report followed on October 9.

An integer overflow is a software error where a calculation produces a number too large for the space allotted to it, so the result wraps around to a much smaller value instead of triggering an error. That is what happened here, and it let the ledger’s built-in exchange hand out XRP that never existed.

Key takeaways

  • A 2015-era flaw in the XRP Ledger payment engine could have minted roughly 18.45 trillion XRP in one transaction.
  • Researcher Cayden Liao and Veria AI reported it on September 22. Version 3.4.1 shipped September 25.
  • RippleX found no evidence of exploitation on any public network.
  • The fix skipped the usual amendment vote, a first for a transaction-processing change on the ledger.

Published: October 11, 2026, 09:30 UTC

How the overflow worked

The attack ran through the XRP Ledger’s decentralized exchange, where accounts post offers to swap one asset for another. An attacker could open hundreds of accounts, each offering a small amount of a token for a large amount of XRP, then fill all of them with one payment.

The payment engine added up the XRP owed using 64-bit integer math with no overflow check, per Crypto Times. When the sum wrapped to a small number, the offer owners were credited in full while the buyer paid almost nothing. The difference was newly created XRP.

The safeguard meant to catch new XRP appearing used the same flawed total, so it missed the discrepancy. A per-account receive limit would not have helped either, because the XRP was spread across hundreds of accounts. The setup reportedly needed only a few hundred XRP, mostly recoverable, plus fees.

Timeline from discovery to disclosure

Veria AI, a security system from Veria Labs, flagged the issue on September 21, according to Cryptonomist. Liao and Veria AI submitted it through the XRP Ledger bug bounty on September 22, rated “Major.” RippleX reproduced it the same day on a standalone server and raised it to critical, confirming the created XRP could fund a later transaction.

The fix was merged into the first 3.4.1 release candidate on September 23 and released September 25. More than 80% of validators on the default Unique Node List were reportedly running 3.4.1 or later on release day. The release notes did not say what the patch fixed.

Why the patch skipped the amendment process

Changes to how the XRP Ledger processes transactions normally ship as amendments, which need over 80% validator support held for two weeks before activating. This fix bypassed that path, with the XRPL Foundation, RippleX and validators jointly approving the shortcut. Crypto Times reports it was the first time a transaction-processing change shipped this way.

The speed came with criticism. Compiled binaries were distributed while the source code for the patch was withheld, which drew objections over the ledger’s open-source commitments. RippleX engineer Mayukha Vadari said on X: “Things have changed with AI. You can’t just sneak in a critical bug patch in a regular public release process.”

A pattern of AI-found flaws

CoinDesk ties the disclosure to a run of long-hidden crypto security bugs surfaced with AI help since July, including a Coldcard wallet flaw behind the theft of at least 1,367 BTC and vulnerabilities that led Core Lightning to tell bitcoin node operators to disconnect. The XRP Ledger bug is the first in that group involving a theoretical break of a major asset’s supply cap.

Crypto security incidents have been frequent this quarter. W3BN has covered the $352 million Bitget hack and $86 million in Ledger-linked wallet thefts. Unlike those cases, no user funds were lost here.

What comes next

Operators still on versions older than 3.4.1 remain exposed to the flaw. The disclosure also activated fixBatchV1_2 and BatchV1_1 on Mainnet on October 9, closing a separate issue in the Batch feature that RippleX found September 22. No Batch amendment was live when that flaw surfaced, so no accounts or funds were affected.

The open question is disclosure practice. With AI tools now able to find old bugs quickly and to reverse engineer patches, teams may stop treating quiet fixes as a workable option.

FAQ

Was the XRP Ledger bug exploited?

No. The XRPL disclosure states, “We have found no evidence that this issue was exploited on any public network.” RippleX reproduced the attack only on a standalone test server, separate from the live ledger, before the fix shipped on September 25.

Who found the XRP Ledger vulnerability?

Researcher Cayden Liao and Veria AI, a security system built by Veria Labs, found it. They reported it through the XRP Ledger bug bounty program on September 22, 2026, and it was rated “Major” before RippleX raised it to critical.

Do XRP holders need to take action?

Holders do not need to do anything. The fix is in server software, xrpld 3.4.1, which validators and node operators run. Anyone operating a node should confirm they are on version 3.4.1 or later.


Staff Correspondent New York, NY

Alex Mitchell is a staff correspondent at Web3BusinessNews covering breaking news and daily developments across the cryptocurrency and blockchain landscape. With over five years of experience in financial journalism and digital asset reporting, Alex delivers fast, accurate coverage of market movements, protocol updates, and emerging trends shaping the Web3 ecosystem.

  • Cryptocurrency
  • Blockchain News
  • Digital Assets
  • Market Analysis
Share it :

Leave a Reply

Your email address will not be published. Required fields are marked *