Osmosis Pauses Alloyed BTC After Nomic Chain Exploit Freezes 22.65 BTC
In brief
- Osmosis froze minting, redemption, deposits, and withdrawals for alloyed BTC after Nomic Chain exploit.
- Emergency upgrade locked 22.65 BTC in attacker's address before stolen funds moved.
- Exploit compromised 39.84 nBTC, representing 36% of total alloyed BTC backing on Osmosis.
- Osmosis plans governance vote to seize frozen BTC and restore full backing via community pool.
The Vulnerability
The exploit targeted a flaw in a custom forwarding mechanism on the Nomic chain, a Cosmos-based blockchain designed to bring Bitcoin into the broader interchain ecosystem. Approximately 39.84 nBTC were compromised in the incident, representing more than a third of the asset backing for alloyed BTC holders on Osmosis.
The fraudulent vouchers made their way to Osmosis via the Inter-Blockchain Communication (IBC) protocol, but the IBC protocol itself was not compromised. The vulnerability lived upstream, on Nomic's side.
Osmosis's Response
Osmosis froze minting, redemption, deposits, and withdrawals for alloyed BTC while moving to contain the damage. Trading of BTC in existing liquidity pools continued despite the freeze, but the suspension of minting and redemptions meant no one could create new alloyed BTC or cash out existing holdings.
This affected roughly 30% of the total BTC exposure across the entire Osmosis exchange. The team moved quickly to prevent further losses.
Recovery Plan
Osmosis outlined a two-part recovery strategy. First, the team plans to propose a governance vote to seize the 22.65 BTC currently frozen in the attacker's address. Second, Osmosis intends to tap the community pool to cover the gap between the frozen BTC and the total amount compromised to restore 1:1 backing of alloyed BTC.
The incident underscores a structural risk in cross-chain asset design. Alloyed BTC aggregates multiple bridged versions of Bitcoin into a single tradeable token, but that design also means a vulnerability in any single backing asset can compromise the integrity of the whole product. Osmosis's response—swift containment followed by community governance—sets a precedent for how DEXs should handle upstream exploits in their backing layers.
