Symbiosis halts BTC bridge after exploit, spotlighting cross-chain risk

Source: bitcoinethereumnews2026/09/12 13:28

Analysis

Symbiosis's decision to halt only BTC routing while leaving other routes live shows how bridge operators are increasingly able to contain damage to a single asset path, but it also confirms that the weak link is message verification rather than Bitcoin's base layer. The attacker exploited BridgeV2's relayer and MPC-signed message flow to mint over 2^62 syBTC on BNB Chain and Ethereum, yet only realized roughly $336,000 because the synthetic supply far exceeded available exit liquidity, a pattern that limits but does not eliminate bridge losses. Coming days after the $320 million Liquid Network breach, this incident strengthens the case that cross-chain infrastructure, not Bitcoin itself, is the recurring failure point. Watch whether Symbiosis publishes a post-mortem on the incorrect message and restores BTC routing, whether syBTC holders face redemption or collateral shortfalls, and whether other MPC-based bridges tighten message validation or pause similar routes.

If you have any feedback or questions about this content, please contact us at crypto.news@kcex.com

The post Symbiosis halts BTC bridge after exploit, spotlighting cross-chain risk appeared on BitcoinEthereumNews.com.

Symbiosis shut down its native Bitcoin bridge on Friday after an attacker exploited its BridgeV2 contract to mint a huge amount of unbacked synthetic BTC. Yet the attacker managed to extract only about $336,000 in real value. The importance of that gap cannot be overlooked. It is important to emphasize that Bitcoin’s security was not compromised, rather it is the infrastructure by which BTC crosses into DeFi that proved to be vulnerable. This incident occurred only days after the Liquid Network breach that resulted in a loss of $320 million, thus making one wonder just how safe the cross-chain infrastructure is after making the observation that Bitcoin is secure, yet its bridges are failing repeatedly. BTC routes halted while the rest of the network stayed open Symbiosis revealed on X that it found evidence of the Bitcoin Bridge attack on September 11 at about 04:28 UTC and stopped BTC routing right away. However, other routing protocols continued to function. In the Delta Incident Archive, the incident is classified as DCI-2026-304, which says that BridgeV2 processed an incorrect message that led to more than 2^62 syBTC being generated on BNB Chain and Ethereum. As a result, the criminal managed to convert a portion of this illegitimate balance into approximately 4.39 WBTC on Ethereum, thereby profiting around $336,000. DeFiLlama classifies the incident as an “Unbacked Cross-Chain Mint.” Where cross-chain trust enters the system Symbiosis documentation shows how heavily the bridge relies on the secure transmission and authentication of cross-chain messages. BridgeV2 connects the protocol’s Portal and Synthesis contracts with its off-chain Relayers Network. Those relayers submit transactions signed through an Multi-Party Computation (MPC) key stored in the contract. Through the use of MPC threshold signatures, native Bitcoin (BTC) is secured in a Portal. This enables relayers to create syBTC on a separate…

Disclaimer: The articles reposted on this website are sourced from public platforms and are for reference only. These articles do not represent the views or opinions of KCEX. All copyrights belong to the original authors. If you believe that any reposted article infringes upon the rights of a third party, please contact crypto.news@kcex.com for removal. KCEX makes no representations or warranties regarding the timeliness, accuracy, or completeness of reposted articles, and shall not be liable for any actions or decisions made based on such content. Reposted materials are for informational purposes only and do not constitute advice, endorsement, or basis for any commercial, financial, legal, and/or tax decisions.