Aztec Connect: $2.1M Stolen From a Bridge With No One Left to Fix It

Aztec Connect, the zero-knowledge privacy bridge built by Aztec Labs, was shut down in March 2023. On 14 June 2026, an attacker walked away with roughly $2.1 million in ETH, DAI, and wrapped staked ETH from the same contract — three years after the team stopped maintaining it and gave up the keys.

What actually happened

According to Halborn's technical writeup and reporting from Cointelegraph, the root cause was a mismatch between two values the bridge used to reconcile rollup proofs with Layer-1 state: the number of transactions a zero-knowledge proof claimed to verify (numRealTxs) and the number of transactions actually applied when the contract updated its state (_numTxs). Those two counts were not guaranteed to match. The contract's proof check only validated part of the submitted proof data, leaving room for transfer instructions elsewhere in the payload to slip through without full verification.

That gap let the attacker submit transactions that credited value inside the bridge without the on-chain backing a correct implementation would have required — in effect, minting withdrawable balance the system never actually received. Yahoo Finance/Cointelegraph reporting indicates the attacker pulled out 909 ETH, 270,000 DAI, 167 wrapped staked ETH, and other assets across seven transactions.

Why nobody could stop it

This is the part that should concern every team running a decentralized protocol, not just Aztec's. When Aztec Labs deprecated Connect in 2023, it deliberately renounced admin control — no multisig, no upgrade path, no pause switch. That's a legitimate decentralization commitment: users don't have to trust a team that could rug them later. But it also means that once a bug is found, there is no one who can stop the bleeding. Aztec Labs confirmed as much on social media, stating it "holds no admin keys or control over the system; it cannot be paused or upgraded." The company was explicit that the incident does not touch the current Aztec network or its token.

Part of a pattern, not a one-off

Web3 Is Going Great, which first flagged the incident, notes that Aztec Connect is only the latest in a run of attacks against dormant smart contracts — Raydium and DxSale have both taken losses from legacy code that could not be deleted, paused, or changed. Blockchain immutability, the same property that makes DeFi credibly neutral, also means an unpatched contract can sit as a live liability indefinitely, waiting for someone to notice the bug before an attacker does.

What this means for teams shipping on-chain

• Decommissioning is a security decision, not a formality. Renouncing admin keys is often the right long-term move for user trust, but it should follow — not precede — a final, thorough audit focused specifically on edge cases in proof/state reconciliation logic.
• Deprecated does not mean dead. If a contract still holds user funds, it is still in your threat model. "We stopped maintaining it" is not a mitigation an attacker respects.
• Proof-verification boundaries need adversarial testing. Mismatches between what a proof attests to and what state changes it actually authorizes are a recurring class of bug in rollup and ZK-bridge designs, not unique to Aztec.

FAQ