The blockchain that was supposed to make moving Bitcoin between exchanges safer just became the attack vector for a $320 million heist.
The Summary
- A blockchain bridge used by multiple crypto exchanges was hacked for $320 million, marking another major breach in digital asset infrastructure
- The hack targets the plumbing layer of crypto—not a consumer wallet or a single exchange, but the infrastructure multiple platforms rely on to move Bitcoin
- Industry leaders including BitGo CEO Mike Belshe and Coinbase's Ryan VanGrack convened to discuss the fallout, signaling this breach hit critical shared infrastructure
The Signal
Blockchain bridges are the weak links everyone knows about but can't seem to fix. This latest $320 million hack proves the point again. When multiple exchanges rely on the same infrastructure to move Bitcoin between chains, that infrastructure becomes a single point of failure. The attacker didn't need to compromise every exchange. They just needed to crack the bridge.
The timing matters. We're deep into a cycle where institutional money keeps flowing into crypto, where Bitcoin ETFs are mainstream, where the pitch is that digital assets are mature enough for serious capital. Then $320 million vanishes through infrastructure that was supposed to be battle-tested.
"The latest in a spate of breaches to shake confidence in digital-asset security."
The immediate response brought together the power players: BitGo's Belshe, who runs one of the largest institutional custody platforms; Coinbase's VanGrack, representing the most visible regulated exchange; AVA Labs' Morgan Krupetsky from the DeFi infrastructure side; and WalletConnect's Jess Houlgrave from the consumer access layer. When that roster assembles to discuss a hack, it's not just another breach. It's a systemic vulnerability being acknowledged.
The real problem isn't that hacks happen. It's that the same class of vulnerabilities keeps working. Bridge protocols have been the attack surface for billions in losses over the past three years. The pattern is consistent:
- Lock assets on one chain
- Issue wrapped tokens on another
- Exploit the validation mechanism in between
- Drain the locked funds
Every major bridge hack follows this script, yet exchanges keep building on shared bridge infrastructure because the alternative is fragmentation. Users want seamless movement between chains. Exchanges want to offer that seamlessness. Bridges promise to deliver it. Then they get hacked.
The Implication
For anyone building in Web3, this is a forcing function. You can't outsource security to shared infrastructure and call it decentralized. The next generation of cross-chain protocols either needs cryptographic guarantees that don't rely on validator honesty, or they need to be explicit that they're trusted services with traditional security models. Stop selling bridges as trustless when they have admin keys.
For asset holders, the message is simpler: if your Bitcoin isn't in cold storage or with a custodian who keeps it on native chain, you're taking bridge risk whether you know it or not. That $320 million didn't vanish from user wallets directly, but someone's balance is about to get a haircut when the losses get allocated. Know where your assets actually live, not just which app shows them.