Chainflip Tron Memo Double-Payout Exploit

On September 13, 2026, cross-chain swap protocol Chainflip halted its network after an attacker abused its Tron settlement path to trigger duplicate payouts, draining 736,442 USDT (about $0.74 million).

What happened

On Tron, swap instructions ride in a transaction's memo field rather than a dedicated contract call. The attacker appended their own memo to a deposit transaction that already carried the validators' signatures. Chainflip's settlement logic did not recognize that the underlying deposit had already been processed, so it treated the added memo as a fresh swap request and paid the same deposit out a second time. The attacker repeated the technique 8 times over roughly 90 minutes — six attempts succeeding — escalating the amount with each pass, and made off with 736,442.17 USDT. One further transfer of 115,654.41 USDT remained locked in the vault and was not stolen.

Aftermath

Chainflip paused the network, secured all unaffected funds, and said the fix had already been designed but needed further verification before a safe restart, which it targeted for at least the following Monday. The team pledged to make affected users whole and said it was tracking the stolen assets across the ecosystem for possible recovery. As no funds had been returned by the attacker as of late September 2026, the status here is stolen.

Why it matters

Chain-specific quirks routinely break assumptions that hold everywhere else: Tron's memo-based instruction model let a signed deposit be replayed as a new order, a class of bug that stricter idempotency and replay protection would have blocked. Like the same-week Nomic nBTC double-spend and Symbiosis fake-syBTC mint, it shows how cross-chain plumbing — not just a protocol's core contracts — is where value quietly leaks out.