Fort Worth 24

collapse
Home / Daily News Analysis / XRP Ledger patched decade-old bug that could create billions of dollars in XRP from nothing

XRP Ledger patched decade-old bug that could create billions of dollars in XRP from nothing

Oct 18, 2026  Twila Rosenbaum  50 views
XRP Ledger patched decade-old bug that could create billions of dollars in XRP from nothing

The XRP Ledger has patched a decade-old software flaw that could have allowed an attacker to create and spend new XRP from nothing, a scenario that would have struck at the core of the cryptocurrency's fixed supply of 100 billion tokens. The issue was serious enough to prompt an emergency software release after researchers demonstrated how a specially crafted payment could produce spendable XRP without the sender funding it.

According to the disclosure, the vulnerability exploited a counting error in the ledger's built-in exchange. The buggy logic could have let hundreds of accounts receive large amounts of XRP while the buyer paid almost nothing, effectively manufacturing value inside the network rather than transferring it. Developers said they found no evidence of exploitation on public networks and fixed the flaw in the xrpld 3.4.1 software release on Sept. 25.

Key facts at a glance

  • The flaw dated to 2015 and affected the XRP Ledger's accounting logic.
  • It could have allowed attackers to create and spend new XRP, violating the ledger's 100 billion token supply cap.
  • The vulnerability relied on a counting error in the ledger's built-in exchange.
  • A crafted payment could have let hundreds of accounts receive large XRP amounts while the buyer paid nearly nothing.
  • No evidence of exploitation was found on public networks.
  • The fix shipped in xrpld 3.4.1 on Sept. 25.

A decade-old accounting flaw

The fact that the bug dated to 2015 is significant. The XRP Ledger has been operating for years, and its codebase has gone through repeated reviews, upgrades and security audits. A flaw surviving for roughly a decade does not necessarily mean it was easy to find or easy to trigger. It means the conditions required to expose it were narrow enough to escape attention, but important enough to require urgent action once researchers found a path. The problem was not a simple crash or a cosmetic error. It involved accounting: the part of a blockchain that determines who owns what and whether a transaction balances.

In most payment systems, the core safety rule is simple. A sender cannot spend more than the sender has. A blockchain adds another layer: every transaction must be validated by network rules, and the resulting ledger state must preserve supply. If a bug lets a transaction pass validation while breaking that balance, the consequences can be severe. In this case, the flaw could have allowed new XRP to become spendable even though no corresponding value was debited from the sender. That is the definition of inflation in a system designed to have none.

How the counting error could have worked

The vulnerability was tied to the XRP Ledger's built-in exchange, a native feature that allows users to trade assets and make payments across different issuances without relying on an external smart contract. The exchange logic has to track offers, balances and payment paths carefully. A counting error in that logic could have caused the ledger to misstate what was owed or what had been paid. Researchers showed that a payment could be structured so the sender did not fund it in the normal way, yet the recipient or recipients still received spendable XRP.

The disclosed impact was not limited to a single account. The flaw could have allowed hundreds of accounts to receive large amounts of XRP while the buyer paid almost nothing. That detail matters because it suggests a scalable exploit rather than a one-off glitch. An attacker who could repeat the pattern across many accounts might have been able to distribute newly created XRP across the network, making detection and recovery harder. The ledger's fixed supply would have been the ultimate casualty: if the bug had been exploited at scale, the market would have had to price in an uncertain and potentially expanding XRP supply.

Why a fixed supply made the bug critical

XRP's supply cap is one of its defining economic properties. The ledger was designed with a maximum of 100 billion XRP, and that limit is central to how users, exchanges and institutional participants think about scarcity. A bug that could create XRP from nothing would not merely be a technical defect. It would be a monetary defect. Even the perception that such a bug existed could undermine confidence, because market participants rely on the software to enforce the supply rule consistently.

That is why the response was framed as an emergency release. Blockchain upgrades often follow scheduled cycles, with testing and coordination across node operators. Security fixes can move faster when the risk is clear. In this case, the risk was not just theft from a single user or a temporary outage. The risk was a violation of the ledger's supply integrity, which affects every holder and every application built on top of the network. A flaw that can mint spendable tokens is categorically different from a flaw that can freeze one account or slow down transaction processing.

The built-in exchange and phantom liquidity

The XRP Ledger's built-in exchange is one of its distinctive features. It allows the ledger itself to process offers and payments involving multiple assets, rather than pushing all trading logic into separate applications. That design can be efficient, but it also means the exchange's accounting code sits close to the core of the system. A counting error in that environment can create phantom liquidity: balances that appear real to the ledger and can be spent, even though they were not backed by a corresponding debit.

Phantom liquidity is especially dangerous in a payment network because it can spread. Once newly created XRP is spendable, it can be moved to other accounts, used in trades or converted into other assets. Each hop makes the original transaction harder to trace and unwind. The fact that the flaw could involve hundreds of accounts points to a distribution risk, not just a single bad balance. Developers would have had to consider not only whether the bug was exploitable, but whether any public network had already seen the pattern.

Emergency release and exploitation checks

The development team said it found no evidence of exploitation on public networks. That is the most important operational detail after the patch itself. A vulnerability that is discovered and fixed before it is used is still a serious security event, but it is not the same as a breach. The absence of evidence does not prove that no attempt was ever made, but it does mean the public ledger did not show the signature of a successful attack. The fix was included in xrpld 3.4.1 on Sept. 25, giving node operators a specific version to deploy.

The release also highlights how blockchain security depends on coordinated upgrades. A patch only protects the network if enough validators and node operators adopt it. In a decentralized system, that process requires communication, testing and monitoring. Emergency releases can be stressful because they compress the normal review window. But leaving a supply-integrity bug unpatched is not a neutral choice. The longer a known flaw remains live, the more time attackers have to study it and the more risk the network carries.

What the patch changes

The patch corrects the counting error in the affected exchange logic and closes the path that could have produced spendable XRP without sender funding. For users, the practical takeaway is that the ledger's supply rule is again being enforced by corrected code on upgraded nodes. For developers and node operators, the takeaway is more procedural: software versions matter, and security releases should be treated as urgent infrastructure updates rather than optional maintenance.

The incident also reinforces why blockchain code is never finished. Ledgers accumulate features, users and value over time. Code paths that were rarely exercised in 2015 may sit near much larger balances years later. A flaw that once looked obscure can become economically critical as the network grows. The XRP Ledger's fixed supply is simple to state, but enforcing it requires every payment, trade and exchange operation to balance correctly. The Sept. 25 patch restores that guarantee for the affected logic, and the absence of exploitation on public networks means the network did not have to confront the alternative: a supply that could have been expanded by anyone who found the right transaction pattern.


Source: Coindesk News


Share:

Your experience on this site will be improved by allowing cookies Cookie Policy