XRP Bridge Drained After Software Accepted Fake Deposits

Operators of a bridge that connects the XRP Ledger to other blockchains discovered attackers drained funds after the bridge’s software accepted forged deposit events as valid. The issue came to light when users reported unexpected outflows and missing funds.

The bridge’s monitoring software appears to have treated simulated or forged deposit messages as confirmed transactions on the XRP Ledger. That triggered the system to mint or release corresponding pegged tokens on the destination chain even though the source ledger did not contain the deposits.

Attackers moved the issued tokens through wallets and decentralized exchanges to convert them to other assets. Bridge operators halted operations to stop further withdrawals and opened an internal investigation.

Maintainers are auditing deposit-validation code paths, reviewing logs to trace the sequence of forged events, and coordinating with other infrastructure providers. They informed exchanges and custody providers that handle the bridge’s wrapped XRP tokens and asked them to monitor for suspicious deposits and to withdraw liquidity if necessary.

Security experts noted the exploit relied on weaknesses in the deposit-verification process, including reliance on single data feeds, insufficient finality checks and incomplete validation of transaction metadata and signatures. Proposed mitigations include requiring cryptographic proofs of inclusion, using multiple independent relayers and validators, adding multi-signature controls for release actions and applying rate limits or timelocks to large or unusual transfers.

The affected operators have not published a full postmortem or a verified total of losses. Users with funds routed through the bridge are advised to check transaction histories and contact counterparties if they observe unexplained transfers. Recovery of drained assets is often difficult when attackers move funds quickly across chains and through mixers or decentralized exchanges.

Bridges that move value between blockchains frequently hold substantial liquidity and must translate state between different ledgers. Technical faults in deposit handling or oracle feeds have previously resulted in losses at other bridging systems.