Nomic nBTC Exploit Freezes 22.65 BTC: What Happened on Osmosis?

The Osmosis exploit involving Nomic’s nBTC system has temporarily disrupted Bitcoin-related operations on the Cosmos-based decentralized exchange. On September 9, an attacker exploited a vulnerability in Nomic’s forwarding mechanism to create fraudulent nBTC through a double-spend.

The incident affected approximately 39.84 nBTC, equivalent to roughly 36% of the backing for Alloyed BTC (allBTC) on Osmosis. An emergency response subsequently prevented the attacker from moving 22.65 BTC, which is now frozen in an address associated with the exploit.

Osmosis has paused allBTC minting, redemptions, deposits, and withdrawals while the teams work on containment and recovery. Importantly, the incident did not involve a direct compromise of Osmosis or the underlying IBC protocol.

Key Takeaways

• The Nomic nBTC exploit involved a double-spend vulnerability that allowed fraudulent nBTC to enter the interchain ecosystem.

• Around 39.84 nBTC was affected, putting approximately 36% of allBTC backing on Osmosis at risk.

• An emergency upgrade froze 22.65 BTC, while recovery now depends on governance and measures to restore full backing.

What Happened in the Nomic nBTC Exploit?

The Nomic bridge hack originated from a vulnerability in Nomic’s custom forwarding infrastructure. Nomic is a Cosmos-based blockchain designed to connect Bitcoin with the interchain ecosystem, including through its nBTC representation of Bitcoin.

The vulnerability allowed an attacker to perform a nBTC double-spend, resulting in the creation of fraudulent vouchers. These assets were subsequently transferred to Osmosis through IBC.

This distinction is important. The exploit did not mean that the IBC protocol itself was hacked. Osmosis was also not directly breached. Instead, the weakness occurred within Nomic's own infrastructure before the affected assets reached Osmosis.

Once the unusual activity was identified, Osmosis halted several functions associated with allBTC to prevent the problem from spreading.

READ ALSO: What is Osmosis AllBtc? Is it BTC or Something Else?

Why Were 22.65 BTC Frozen?

The incident involved approximately 39.84 nBTC, creating a significant gap in the assets supporting Alloyed BTC on Osmosis.

An emergency chain upgrade was used to restrict the attacker's ability to move the affected Bitcoin. As a result, 22.65 BTC frozen in the attacker's address could no longer be transferred normally.

The frozen amount is important because it represents a substantial portion of the funds connected to the incident. However, freezing the BTC does not by itself resolve the backing shortfall. The remaining difference must still be addressed before the affected system can return to full 1:1 collateralization.

Osmosis has therefore kept key allBTC functions restricted while the recovery process moves forward.

How Did the Exploit Affect Alloyed BTC?

Alloyed BTC, commonly referred to as allBTC, is designed to combine different bridged Bitcoin assets into one unified Bitcoin representation on Osmosis.

That structure creates an important risk: if one of the assets contributing to the pool's backing becomes compromised, the impact can extend beyond that individual bridge.

In this case, the compromised nBTC represented about 36% of allBTC's backing. The incident therefore raised questions about whether each allBTC token could continue to be fully backed by Bitcoin while the affected nBTC was being investigated.

Osmosis responded by stopping new allBTC minting and redemption activity. Osmosis BTC withdrawals connected to the affected asset were also suspended as part of the containment process.

Trading within existing liquidity pools may continue, but this is different from being able to freely mint or redeem allBTC for its underlying backing.

What Is the Recovery Plan?

Osmosis has indicated that recovery will involve governance and community resources.

One proposed step is a governance vote concerning the 22.65 BTC frozen in the attacker's address. A successful proposal could authorize action involving those funds.

The second part of the plan involves using the community pool to address the remaining shortfall. The objective is to restore the allBTC backing to a full 1:1 ratio so that affected holders are properly collateralized.

The final outcome depends on governance decisions, technical recovery measures, and the details of the forthcoming incident report. Until those steps are completed, users should not assume that allBTC minting and redemption will immediately return to normal.

What Does the Osmosis Incident Mean for Cross-Chain Bitcoin?

The Nomic bridge hack highlights a broader issue with cross-chain assets: security depends on more than the main blockchain or messaging protocol.

IBC can securely transmit information and assets between supported chains, but applications and custom bridge mechanisms built around it can introduce additional risks. A vulnerability in one component can potentially affect assets elsewhere in the ecosystem.

The Nomic incident also demonstrates why collateral composition matters. Because nBTC represented a large share of allBTC's backing, a problem affecting one Bitcoin representation had consequences for a broader synthetic asset.

For users, the incident is a reminder to examine not only where a token trades, but also what assets support it, how those assets are bridged, and what happens if one backing component fails.

What Happens Next?

The immediate focus is the recovery of the affected Bitcoin and the restoration of allBTC's backing.

Osmosis users should watch for updates on the governance proposal, the treatment of the frozen funds, and the community-pool mechanism intended to cover the remaining shortfall. The status of minting, redemption, deposits, and withdrawals will also determine when normal allBTC operations can resume.

The incident remains a developing cross-chain security event. Until the recovery process is completed, users should treat announcements from Osmosis and Nomic as the primary source for operational updates rather than assuming that normal withdrawal or redemption functionality has returned.

READ ALSO: Will the Fed Hold or Hike Rates in September 2026? Crypto Market Impact Analyzed

Conclusion

The Osmosis exploit was ultimately linked to a vulnerability in Nomic's nBTC infrastructure rather than a direct breach of Osmosis or IBC. The Nomic nBTC exploit affected around 39.84 nBTC and put roughly 36% of Alloyed BTC's backing under pressure.

Osmosis responded by restricting affected operations and freezing 22.65 BTC connected to the attacker. The next stage depends on governance approval, recovery of the frozen assets, and measures to restore full backing for allBTC.

For crypto users, the incident underscores the importance of understanding bridge architecture and collateral risks before using cross-chain assets.

If you are looking for a broader platform to monitor Bitcoin and other crypto markets while these developments unfold, you can explore the trading tools and market access available through Bitrue and create an account when ready.

FAQ

What is the Nomic nBTC exploit?

It was a vulnerability that enabled an attacker to double-spend nBTC and create fraudulent assets.

How much BTC was frozen on Osmosis?

An emergency response froze approximately 22.65 BTC linked to the attacker.

How much nBTC was affected?

Around 39.84 nBTC was involved in the incident.

Was Osmosis directly hacked?

No. The vulnerability originated in Nomic's infrastructure, while IBC and Osmosis were not directly compromised.

Are Osmosis BTC withdrawals available?

Withdrawals and other affected allBTC operations were paused while the incident was being contained and the recovery plan was developed.

Disclaimer: The views expressed belong exclusively to the author and do not reflect the views of this platform. This platform and its affiliates disclaim any responsibility for the accuracy or suitability of the information provided. It is for informational purposes only and not intended as financial or investment advice.