The asset breakdown paints a clear picture of the theft:
Rather than immediately cashing out everything, the attacker took a staggered approach. PeckShield tracked a portion of the stolen funds moving through ChangeNOW, a non-custodial swap service, and Binance, the world's largest centralized exchange .
However, the most notable detail for on-chain sleuths is what the hacker didn't move. As of the latest monitoring updates, the attacker's wallet still held 2,102 ETH, worth approximately $4.23 million . That suggests the exploiter converted the stolen stablecoins and tokens into ETH but paused before fully cashing out—possibly wary of triggering additional exchange freezes or law enforcement attention.
The attacker's retained balance represents a live on-chain footprint. Security researchers and blockchain analytics firms continue to track the wallet, and any future movement will likely trigger alerts across major compliance platforms .
Gravity Bridge is a decentralized, trustless blockchain built to connect the Ethereum and Cosmos ecosystems via the Inter-Blockchain Communication (IBC) protocol. It enables users to transfer ERC-20 assets like USDC, DAI, and WETH into the Cosmos universe and vice versa, without relying on a centralized custodian .
By mid-2026, Gravity Bridge had accumulated over $50 billion in cumulative bridged volume and operated with a 100+ validator set for settlement finality . The bridge was designed for neutrality and permissionless access, with governance spread across multiple stakeholders. Before the May 30 exploit, its total value locked (TVL) sat at roughly $11.5 million, according to on-chain tracking cited in coverage of the incident
.
The breach exposed a fundamental tension in bridge design. Gravity Bridge's architecture is decentralized at the governance and validator level, but the use of privileged signing keys to authorize Ethereum-side withdrawals introduced a concentrated point of trust. When that key was reportedly compromised, the attacker could drain funds without defeating the bridge's broader security model .
The Gravity Bridge exploit was not an isolated incident. By mid-May 2026, PeckShield had already recorded eight major cross-chain bridge hacks totaling $328.6 million in stolen assets across 2026 . The list includes:
| Date | Protocol | Reported Loss |
|---|---|---|
| May 18 | Verus-Ethereum bridge | $11.4 million |
| May 15 | THORChain | $10 million |
| April 27 | ZetaChain | $300,000 |
| April 18 | Kelp / LayerZero | $292 million |
| April 13 | Hyperbridge | $2.5 million |
| April 7 | Squid Router | $1 million |
| February 21 | IoTeX bridge | $8.8 million |
| February 1 | CrossCurve | $3 million |
Gravity Bridge becomes the ninth major addition to this grim tally, likely pushing the 2026 total beyond $330 million before June. The frequency and scale of these incidents have elevated bridge security to one of the industry's most urgent problems .
If there is a common thread running through these exploits, it is not necessarily code quality but key management architecture.
The Kelp/LayerZero incident in April accounted for $292 million alone, and like the Gravity Bridge event, it raised questions about authorization mechanisms rather than purely technical bugs. When a bridge's security relies on a small set of signing keys—even if those keys are held by respected parties—any single compromised key can become a skeleton key for an attacker .
The Gravity Bridge exploit reinforces an argument security researchers have been making for years: decentralized consensus at one layer of the stack does not compensate for centralized key management at another. Multi-party computation (MPC) wallets, threshold signing schemes, and hardware security modules (HSMs) have all been proposed as mitigations, but adoption remains inconsistent across the bridge landscape.
The incident also highlights a pragmatic reality for investigators. Because the attacker swapped stolen stablecoins into ETH and left the majority in a traceable wallet, the breach becomes a live case study for asset recovery and legal tracking. Whether that leads to a return of funds, or simply another address added to an endless on-chain blacklist, remains to be seen.
Comments
0 comments