Taiko L2 Bridge Exploit Drains $1.7 M After SGX Key Leak

A attacker siphoned roughly $1.7 million from Taiko’s Ethereum L1 bridge and ERC‑20 vault by forging withdrawal proofs with a private SGX signing key that had been accidentally published on GitHub, forcing the L2 network to stop block production on June 22 2026 [1].

How the exploit unfolded

Taiko’s bridge relies on cryptographic proofs generated by Raiko, a multi‑prover stack that uses Intel SGX enclaves. The enclave’s signing key, an RSA‑3072 private key, was mistakenly committed to the public taikoxyz/raiko GitHub repository. With that key, the attacker enrolled their own SGX provers as legitimate participants, produced forged L2 state attestations, and passed them to the L1 bridge’s processMessage() function. The bridge then marked the bogus withdrawals as RETRIABLE, allowing the retryMessage() call to release real assets from the Ethereum‑side vault [2].

Blockaid’s real‑time detection system flagged the abnormal flow, and Taiko’s team froze the bridge by 2:08 AM ET, halting all L1 bridge withdrawals. The attacker moved about 2 million TAIKO tokens—worth roughly $170 k at the time—to a MEXC exchange address before the freeze [1].

Market reaction and broader context

The immediate market impact was a sharp decline in the TAIKO governance token, which fell about 10% to near its all‑time low of $0.07, according to CoinGecko data [2]. The broader L2 ecosystem has seen similar bridge attacks this year, accounting for more than $340 M in losses across multiple protocols, highlighting a systemic risk in cross‑chain designs [1].

What to watch

• Bridge key management – monitor any announcements from Taiko about revised secret‑handling procedures or hardware security module (HSM) integrations.
• Token price levels – watch the $0.06–$0.08 range as potential support/resistance zones given the recent 10% slide.
• Future unlocks – track the scheduled release of the 2 million TAIKO tokens held by the attacker, which could affect supply dynamics once recovered or sold.

The incident underscores that even a single leaked credential can collapse a hardware‑trusted bridge model, reminding developers that operational security is as critical as cryptographic design in multichain environments.