Echo Protocol: A Stolen Admin Key Printed $77M of Fake Bitcoin, and the Thief Got $822K

At 21:21 UTC on Monday 18 May 2026, someone created 1,000 eBTC on the Monad blockchain. Each eBTC was supposed to stand for one real Bitcoin held in reserve by Echo Protocol, which made the batch worth about $77 million on paper. There was no Bitcoin behind any of them. The person who made them had taken control of the one key allowed to print them.

A pseudonymous trader who posts as DCF GOD spotted it within minutes and raised the alarm on X. The security firm PeckShield and the on-chain trackers Lookonchain and Onchain Lens followed. By the time the dust settled the attacker had turned 45 of the fake tokens into real money, sent about 384 ETH, roughly $822,000, through the Tornado Cash mixer, and was left holding 955 eBTC that nobody could buy. Echo then regained control and burned them. Echo's own estimate of the loss was about $816,000.

The gap between $77 million and $822,000 is the whole story. Printing money is easy with the right key. Spending it is not.

What eBTC was meant to be

Echo Protocol sells itself as a Bitcoin liquidity and yield platform. Its main home is Aptos, a blockchain built by former Meta engineers, where it issues a token called aBTC. It later expanded to other chains, including Monad, a fast Ethereum-compatible blockchain that launched in late 2025, where its token is eBTC.

These are wrapped Bitcoin tokens. Bitcoin cannot move onto other blockchains by itself, so a project holds real Bitcoin and issues tokens elsewhere that represent it, much like a depositary receipt lets a share listed in one country trade in another. The receipt is only as good as the promise that each one is backed by a real coin. Holders can then lend, borrow or earn interest with their Bitcoin in DeFi, the set of lending and trading apps that run on blockchains instead of through banks.

Somebody has to be able to create new receipts when new Bitcoin arrives. On Echo's Monad contract that power belonged to an admin role, a master key that could grant and revoke every other permission, including the right to mint, meaning to create new tokens.

One key, no brakes

Echo said the attack came from a compromised admin key on its Monad deployment, not from a bug in its code. Independent analysts who examined the contract found the admin role was held by a single ordinary wallet. There was no multisig, which would have needed several people to approve, the way a company account needs two directors' signatures for a large payment. There was no timelock, a built-in delay that would have given anyone watching time to react. There was no cap on how many eBTC could exist and no limit on how fast new ones could be made.

With the key, the attacker ran a short sequence: granted itself the admin role, granted itself the minter role, revoked the original admin so the team was locked out, and minted 1,000 eBTC to its own address in one transaction. How the key was stolen has not been made public.

Why the thief only got $822K

A fake share is worth only what someone will pay for it before the fraud is spotted. Monad is a young chain and there was very little money in its markets for eBTC. Dumping 1,000 of them would have collapsed the price at once.

So the attacker borrowed instead. Curvance, a lending app on Monad, accepted eBTC as collateral and valued it as Bitcoin, the way a pawnbroker might accept a forged gold bar without assaying it. The attacker deposited 45 eBTC, then valued at about $3.45 million, and borrowed about 11.29 WBTC, a different and genuine wrapped Bitcoin, worth roughly $868,000. Lending apps let borrowers take out only a fraction of their collateral's value, which kept the haul small. The WBTC was moved to Ethereum, swapped for ETH and fed into Tornado Cash, which pools deposits so they cannot be traced.

That left 955 eBTC sitting in the attacker's wallet with nowhere to go. Nick Sawinyh, founder of the DeFi research site DeFiprime, wrote that the rest of the fake supply was stuck because Monad's lending and trading markets were too shallow to absorb it. Early on 19 May Echo said it had "successfully regained control" of its admin keys and burned all 955.

Who is left holding the loss

Curvance said its contracts were not compromised and that its isolated market design, where each market is ring-fenced from the others, kept the damage inside one eBTC pool, which it paused. That still left lenders in that pool facing a WBTC loan backed by worthless collateral. Echo paused its Monad cross-chain functions, upgraded the Monad contract to restrict the affected operations, fully paused its Aptos bridge and suspended Echo Aptos Lending, while saying it had found no evidence of compromise on Aptos. Its Aptos exposure was about $71,000, with no confirmed loss.

On 30 June Echo opened a claims process: affected users had two weeks to file a ticket on its Discord server with their wallet address and losses. Echo said any follow-up plan would need agreement from other platforms involved, Curvance among them. As of mid-October no payout amount or schedule had been made public, and the attacker had not been identified.

Misha Putiatin, co-founder of the restaking project Symbiotic and the security firm Statemind, told Decrypt that projects leaning on off-chain infrastructure should expect "a resurgence of 'Web2.5' style attacks" aimed at how keys are managed. Echo was one of 13 DeFi breaches DefiLlama counted in May 2026 alone. Its real damage was modest. The lesson was not: a single unguarded key could print $77 million, and the only thing that stopped it being $77 million was that nobody wanted to buy.