The L2 solution Taiko has successfully restored its cross-chain bridge 10 days after an incident in which attackers withdrew assets worth $1.7 million. All affected users have already received full compensation for their losses.

Attack Details and Consequences

The incident occurred on June 22. The hack was caused by a compromised SGX signing key that was mistakenly exposed in a public GitHub repository. This allowed the attacker to sign fraudulent transactions and withdraw funds from the bridge's liquidity pool.

The Taiko team responded promptly: the vulnerability was fixed, and the bridge's reserves were restored to a 1:1 ratio. An independent third-party audit of the code and infrastructure was conducted to confirm the protocol's security.

Recovery and Lessons for the Industry

The restoration of the bridge and the return of funds are a positive signal for the ecosystem. However, the fact that a critical signing key was leaked through a public repository is a serious operational security failure. This serves as a reminder that even advanced L2 solutions must implement multi-layered key protection and strict CI/CD processes.

The event also highlights the vulnerability of SGX technology in the context of cross-chain bridges: trust in hardware should not be the sole barrier. Ideally, projects should combine hardware modules with multi-signature schemes and oracles for transaction verification.

My analysis: Taiko handled the crisis admirably, but the cost of the mistake could have been much higher. The incident is yet another reminder that in DeFi, key security must be an absolute priority, not just a checkbox in an audit.