Skip to content
Blockchain Posts

exploit

Taiko halts L2 block production after bridge proof-verification exploit

Taiko's chain state verification was compromised on June 22; proposers stopped producing blocks, the ERC20 Vault on Ethereum was drained for an estimated $1.7M, and all bridges are flagged unsafe.

by 5 min read
exploitethereumtaikoinfrastructureon-chain

Ethereum L2 Taiko Alethia confirmed on June 22, 2026 that its chain state verification mechanism was compromised and that the security assumptions of every bridge deployed on the network can no longer be relied upon. All Taiko proposers stopped producing new blocks while the team investigates, leaving the network at a standstill as a containment measure. Initial loss estimates put the figure at around $1 million (Blockaid) and $1.7 million (PeckShield), drained from Taiko's ERC20 Vault on Ethereum L1.

What happened

Taiko's security notice, posted to the @taikoxyz X account, is unusually blunt for an active-incident communication:

We have confirmed a compromise of Taiko's chain state verification mechanism. As a result, the security assumptions of all bridges deployed on Taiko can no longer be relied upon.

The team followed up with a coordination statement: "We are actively coordinating with the Security Council and ecosystem partners to contain the incident, pause affected systems where possible, and take all necessary technical and legal actions." Users were told to withdraw immediately from affected bridges.

Within hours, proposers — the set of operators responsible for batching L2 transactions for proving and settlement on Ethereum — coordinated a halt to block production. Taiko Alethia ceased to advance state. Withdrawals through the canonical bridge continue to be processed against the last verified state, which is what Taiko's notice is asking users to act on while they still can.

The Block was first to confirm the network-wide pause in its piece Ethereum Layer 2 Taiko halts block production following exploit.

Mechanism — message proofs without matching events

Security firm Blockaid identified the primitive in its preliminary analysis:

Crafted message proofs were accepted as valid on Ethereum L1 without corresponding legitimate MessageSent events on the Taiko source chain.

In plain terms: Taiko's bridge on Ethereum verifies cross-chain messages by checking a source-signal proof that a corresponding event was emitted on Taiko L2. The compromise let the attacker present proofs that the L1 verifier accepted, without an actual matching MessageSent event ever being emitted on L2. With the verifier convinced, the bridge released funds from the ERC20 Vault as if it were honouring a legitimate L2→L1 withdrawal.

This is a chain-state-verification failure, not a multisig key compromise — the same class as past zk-rollup proof flaws, but here on Taiko's based-rollup architecture. The team has not yet published the specific contract path or the precise bug; that detail is what the Security Council pause is buying time to publish without giving an active attacker a roadmap.

Numbers

- Loss range (initial)             : ~$1.0M (Blockaid) - $1.7M (PeckShield)
- Asset drained                    : ERC20 Vault on Ethereum L1
- Token traced to exchange         : ~1.99M TAIKO (~$169,702) sent to MEXC
- Block production status          : halted by all proposers
- Bridges affected                 : all bridges deployed on Taiko Alethia
- Root cause (preliminary)         : source-signal proof verification flaw
- Date confirmed by team           : 2026-06-22

Sources: Blockaid, PeckShield, Taiko team statement.

USD figures are at the time of the incident; the TAIKO movement to MEXC is the most concrete on-chain breadcrumb publicly reported at this stage.

Impact

  • Users with active bridge positions on Taiko Alethia: the canonical bridge contracts are flagged unsafe. Anyone holding assets on L2 should treat Taiko's "withdraw immediately" notice as the operative instruction until a fixed deployment ships.
  • Liquidity protocols on Taiko: any application whose collateral or accounting depends on L2 state advancing is now stuck. With proposers halted, no new state roots settle; deposits and withdrawals through the canonical bridge are limited to what was already finalised before the pause.
  • TVL bridged via Taiko's ERC20 Vault: at risk to the extent of the exploit's reach. The asymmetry between Blockaid's ~$1M figure and PeckShield's ~$1.7M figure reflects whether further crafted proofs are still pending; the final number depends on what the Security Council manages to invalidate before the next checkpoint.
  • The L2BEAT risk profile: Taiko Alethia's stage classification will be revisited. The system's reliance on a single verification path that just failed is exactly the kind of finding that re-opens the "no stage" debate for based rollups.

What to watch

  1. The post-mortem and the patch. Taiko has not yet published the specific contract path. Watch the taikoxyz/taiko-mono repository and its security advisories page for a GHSA filing and a fix PR. The patch will dictate whether withdrawals resume against the existing canonical bridge or via a new deployment.
  2. Security Council action. Taiko's Security Council is the body now coordinating containment. Any on-chain pause or upgrade transaction it executes is the receipt of how recovery is being handled.
  3. Exchange freezes downstream of MEXC. The ~1.99M TAIKO sent to MEXC is the most actionable on-chain trail. A public statement from MEXC — freezing the deposit address or returning funds — would be the first concrete recovery signal.
  4. Whether proposers resume. Block production restart is the operational signal that the verification path has been fixed (or routed around with a temporary multi-sig safeguard). Until proposers come back, the L2 is paused and the bridge is the only live surface.

Context — the second L2 bridge proof compromise this quarter

This is the second incident this quarter where a rollup bridge's proof-verification path — not its operator keys — was the failure mode. It rhymes with the Aztec Connect rollup processor V3 zk-proof drain of $2.19M in early June, where Slowmist traced the loss to a verifier the team had deprecated but left callable. Taiko's incident is technically distinct — the verification logic itself was compromised, not a stale verifier left online — but the pattern is the same shape: an L2 bridges value to L1 based on a single proof-acceptance contract, and when that one contract fails, the bridge fails open.

DefiLlama's tracker now counts more than 20 crypto-related incidents in June 2026 alone. The June 22 entry is the largest L2 architectural failure of the month.

Sources:

Related stories