Axelar Secret Network Hack Drains $4.67M via IBC Bridge

High attention and emotional sentiment detected.

Both teams shared near-identical statements at about 13:40 UTC. According to Axelar’s thread, the fault sits in the Secret-side ICS-20 contract. That contract handles assets bridged from Axelar to Secret.

What Axelar and Secret Disclosed

Axelar said the incident hit assets bridged over IBC to Secret. Immediately upon awareness, its emergency committee disabled the Secret and Secret-SNIP connections.

The team stressed that the damage stayed contained. According to the statement, Axelar’s core protocol was not affected. No other IBC connections or native Secret tokens appear impacted.

Secret Network posted a matching message at nearly the same minute. As a result, both teams framed this as a coordinated, joint disclosure. Neither side pointed fingers.

Axelar also said it is contacting exchanges and law enforcement. Meanwhile, the team is preparing a detailed post-mortem. That report is not public yet.

The Bridge at the Center of the Incident

Axelar is a cross-chain network. It links Cosmos and EVM ecosystems through its own chain and a messaging layer called GMP.

Secret Network is a privacy-focused smart contract chain. It uses trusted execution environments, so its code is public but its data stays encrypted.

The two connect over IBC, the Cosmos standard for cross-chain transfers. This specific route moved assets from Axelar into Secret since roughly 2022. Now that route is frozen.

How the ICS-20 Bridge Exploit Worked

ICS-20 is the Cosmos standard for moving tokens between chains over IBC. It verifies a packet, then mints or releases a matching token on the receiving chain.

On Secret, that contract handles incoming assets bridged from Axelar. So the flaw appears to live in how it validated those incoming transfers.

According to Axelar and early forensics, token representations could appear without a valid incoming packet. In other words, it resembles a classic unbacked minting bug.

Still, the precise root cause stays unconfirmed for now. The affected code sits in the public ics20-for-axelar repository. The promised post-mortem should detail the exact fault.

Why Secret’s Privacy Hides the Attacker

Secret Network encrypts balances and transfers by default. Because of that design, the exploit transactions and the attacker’s wallet stay hidden from public explorers.

This privacy normally protects ordinary users. However, it also slows attribution. It complicates any attempt to trace or freeze the stolen funds.

Researchers have still pinned down the victim contract. Coverage from The Crypto Times points to secret1yxjmepvyl2c25vnt53cr2dpn8amknwausxee83. That account is the gateway for the Axelar bridge channels.

You can view it on Mintscan. Even so, the encrypted ledger keeps the exact malicious calls invisible on-chain.

Another Bridge Falls to a Contract Bug

Cross-chain bridges remain a favorite target for attackers. Over recent years, contract bugs and packet flaws have drained large sums across the industry.

This case fits that pattern, yet the response stands out. According to both teams, the kill switch landed within minutes of detection.

That speed matters. Because the connections went down fast, the affected route could not bleed further while the teams investigated.

Axelar has leaned on its emergency committee before. This time, that same playbook isolated the damage to a single Secret-side contract.

Market Impact From the Axelar Secret Network Hack

The financial damage looks modest against Secret’s footprint. According to DefiLlama, Secret Network’s total value locked sits near $1.53 million.

Price reaction stayed limited in the first hours. SCRT traded around $0.055 to $0.058. AXL hovered near $0.045, with only minor moves.

One outlet, ValueTheMarkets, reported the loss closer to $4.3 million. Most sources, though, cite the ~$4.67 million figure from Axelar directly.

None of this is financial advice. Always verify on-chain data and primary statements before acting on any exploit report.

How the Crypto Community Reacted

Reactions on X stayed mixed but measured. Many users praised the quick shutdown and the transparent, joint statement.

Others voiced familiar bridge fatigue. Some replies argued that cross-chain bridges keep failing as a category.

Still, the dominant note leaned toward relief. Because the teams contained the leak fast, several observers called the situation under control.

What Comes Next for Axelar and Secret

Several key questions stay open. The teams have not released a token breakdown, an attacker identity, or any recovery status.

For now, the disabled connections keep the affected route frozen. According to both teams, that containment should prevent further loss.

The next milestone is the post-mortem. Once Axelar publishes it, the report should confirm the bug, the assets taken, and any plan to repay users.

Watch the Secret Network and Axelar channels for that update. The Axelar Secret Network hack is recent, so expect the official picture to sharpen soon.