Bridge entity

Axelar–Secret IBC Bridge

Axelar–Secret IBC Bridge is the asset-transfer connection used by Secret Tunnel for Axelar-wrapped assets on Secret Network. In June 2026, the Secret-side ics20-for-axelar contract accepted inbound token messages without authenticating the legitimate source channel, enabling unbacked wrapped-asset minting and redemption against real Axelar-side reserves. The affected connection was disabled and remains non-operational at the latest review.

pausedreviewedcurrent

Bridge facts

Canonical name
Axelar–Secret IBC Bridge
Type
Asset Bridge
Status
Paused
Confidence
High
Primary chains
Secret Network, Axelar
Primary assets
USDT, USDC, WETH, WBTC, DAI, WBNB, wstETH
Operator
Secret Network ecosystem / Axelar integration
Ecosystem
Secret Network
Launch date
2023-03-30
End date
Unknown
Terminal reason
Not applicable / unknown
Last reviewed
2026-08-21
Last verified
2026-08-21

Incident cases

  • Axelar–Secret IBC Bridge 2026 source-channel validation exploit2026-06-10

    On June 10, 2026, the Secret-side ics20-for-axelar contract accepted inbound cross-chain token messages without authenticating the expected source IBC channel. An attacker used that verification gap to mint unbacked Axelar-wrapped assets on Secret and redeem them through the legitimate Axelar connection against real reserves. Secret reported approximately USD 4.67 million stolen. The connection was disabled, no returned attacker funds are established in the admitted record, and a later Axelar governance vote only signaled a non-binding future freeze/recustody and victim-distribution path.

    Exploitabout USD 4.67 millionUnresolved

Evidence records

Official URL status

Official URL recorded as live_verified: https://tunnel.scrt.network/
Independent incident archive

Help maintain bridge history

Support incident linkage, lifecycle updates, evidence preservation, broken-link replacement, and corrections.

Support BIR
Record maintenance

Report a correction

Report missing evidence, incorrect dates, outcome changes, recovery details, reimbursement status, or broken links. GitHub Issues are preferred for structured review; the Google Form is available if you do not use GitHub.