Bitcoin, Ethereum-linked protocols lose $35 million in multiple attacks hours apart

We talk a lot about the security of Bitcoin and Ethereum as base layers. The math works, the consensus holds, and the networks themselves are effectively unhackable at current hash rates. But that reality doesn't matter if the plumbing connecting them is held together by duct tape and high-trust assumptions. This week, we saw exactly how fragile that plumbing is when multiple protocols, including Verus and B² Network, were drained of roughly $35 million in a matter of hours.

As a builder, you need to look past the headline numbers. The real story here isn't the lost capital; it's the specific failure points that allowed it to happen. We aren't seeing sophisticated cryptographic breaks. We are seeing basic operational failures, compromised keys, and the inherent risks of upgradeable contracts. If you’re building in the cross-chain space, this is a loud warning that your greatest vulnerability isn't the code you wrote, but the permissions you kept.

The Multi-Chain Mirage

Cross-chain protocols like the B² Network are designed to make Bitcoin behave more like Ethereum. It’s a noble goal. Everyone wants to unlock the dormant capital sitting in BTC wallets. However, to make these bridges work, developers often rely on intermediate layers or multisig wallets that act as the custodian for locked assets.

The recent attacks demonstrate that these bridges are essentially honeypots with centralized backdoors. In one instance, the attacker didn't have to break the protocol's validation logic; they simply gained control over the keys that allowed for contract upgrades or administrative actions. Once you have the keys to the kingdom, the underlying security of the blockchain is irrelevant. You are effectively the protocol at that point, and you can tell the smart contract to send the funds wherever you want.

The Governance Trap

Many founders believe that having an upgradeable contract is a safety feature. It allows you to fix bugs or respond to emergencies. But in practice, these upgrade powers are the primary target for malicious actors. If a hacker can compromise the developer wallets or social engineer their way into a multisig, they can swap a secure contract for one that includes a drain function.

For those of us building in this space, we have to ask: at what point does the risk of centralized control outweigh the benefit of being able to patch code? At STKR News, we have always been skeptical of "decentralized" protocols that can be fundamentally altered by a few people behind a curtain. The recent $35 million loss shows that this skepticism is grounded in financial reality.

Why Sophisticated Validation Failed

One of the more frustrating aspects of these specific attacks was the failure of validation checks. In theory, these protocols check the validity of transactions before they are processed. However, when the validation logic itself is bypassed or compromised at the administrative level, the checks become theater. It's like having the world’s most secure vault door but leaving the spare key under the welcome mat.

Builders need to move toward immutable systems, but the market demands fast iterations. This tension is where the hacks happen. If you are building a bridge or a Layer 2, you are operating a bank. If your bank can be robbed because someone stole a laptop or phished an employee, you aren't building a decentralized future; you're building a fragile fintech app on top of a blockchain.

Lessons for the Founder

If you're in the trenches building these systems, there are three immediate takeaways from this week's events. First, you need to minimize the power of your administrative keys. If a single point of failure exists, it will eventually be exploited. Consider time-locks for upgrades, where changes are announced days before they go live, giving users a chance to exit if they see something suspicious.

Second, stop relying exclusively on multisigs for high-value custody. Multisigs are better than single keys, but they are still susceptible to coordinated attacks or internal collusion. We need to see more adoption of threshold signature schemes (TSS) and more robust, decentralized validator sets that don't rely on the founder's roommates to sign off on transactions.

Third, we have to be honest about the trade-offs of the "Bitcoin Layer 2" narrative. Many of these projects are essentially custodial wrappers. That's fine if users know the risks, but marketing them as having the security of Bitcoin is misleading at best and dangerous at worst.

The Skeptic's View

I want to see Bitcoin and Ethereum work together. I want to see a world where assets move seamlessly across chains. But the current architecture is clearly not ready for prime time. $35 million is a drop in the bucket compared to what's at stake as these networks grow. If we can't secure a few protocols today, how are we going to secure the trillions of dollars that the industry claims it wants to bring on-chain?

The builders who survive the next few years will be the ones who prioritize security over speed. They will be the ones who ship slower because they are focused on removing their own ability to touch user funds. It isn't flashy, and it doesn't make for great marketing Copy, but it's the only way to build something that actually lasts.

The industry is learning a hard lesson: you cannot hide centralized risk behind decentralized terminology forever. Eventually, the math catches up.

We are still in the experimental phase of cross-chain infrastructure. These hacks are a reminder that the experiments are expensive and the participants are often the ones paying the bill. As a founder, your job is to reduce the blast radius. If your protocol is compromised, can you protect the rest of the ecosystem? If the answer is no, you might want to rethink your architecture before the next wave of attacks hits.

Read the original at CoinDesk →