Axelar Network Loses $4.67M in Secret Bridge Hack, Core Unaffected

Axelar Network disclosed a security incident that drained roughly $4.67 million from its cross-chain bridge connecting to Secret Network. The team announced the breach in a post on X on June 19, saying it immediately disabled that bridge link to contain further losses.

The exploit targeted the bridge specifically. Axelar’s Core Protocol – the underlying infrastructure that routes messages across blockchains – was not compromised and continues operating normally, the project stated. An investigation is underway to determine how attackers pulled off the heist and assess the full damage. Axelar said it is also rolling out additional security measures.

This is the latest in a long line of bridge hacks that have plagued crypto over the past few years. Bridges are a notoriously fragile piece of infrastructure in decentralized finance – they hold locked assets from multiple chains, making them prime targets. Past breaches at Wormhole, Ronin, and Multichain each resulted in losses of hundreds of millions of dollars. While $4.67 million is far smaller in comparison, the incident reinforces a persistent trust problem: users moving assets across chains still rely on these middlemen, and one broken link can cost millions.

Axelar provides a general-purpose cross-chain communication layer, connecting assets and data across dozens of blockchains. The Secret Network integration allowed private smart contract data to flow between Secret and other ecosystems. That link is now severed until further notice.

For traders holding positions that depend on Axelar’s Secret bridge, the immediate risk is locked liquidity. No timeline was given for reopening the connection. Those using other Axelar bridges – like those to Ethereum, Cosmos, or Avalanche – appear unaffected, but the market may price in a broader security discount across Axelar’s ecosystem tokens.

The team promised a detailed post-mortem after the investigation concludes. Until that report lands, the crypto community will watch for any signs of deeper vulnerability inside the core protocol. The incident also raises a practical question: even when core layers remain safe, can any bridge be considered "secure enough" after so many failures?