Dev.to Security 🔐 Cybersecurity 👁 0 📖 4 min read

Aztec Connect was shut down in 2024. It still lost $2.19M.

On June 14, 2026, an attacker drained about $2.19M from Aztec Connect's RollupProcessorV3 contract. Aztec Connect had been shut down three years earlier. Admin keys were surrendered in 2024. The contract became immutabl

Aztec Connect was shut down in 2024. It still lost $2.19M.

On June 14, 2026, an attacker drained about $2.19M from Aztec Connect's RollupProcessorV3 contract.

Aztec Connect had been shut down three years earlier. Admin keys were surrendered in 2024. The contract became immutable. There was nothing left to exploit except the fact that it still existed and still held money.

Cartoon: a factory marked CLOSED 2024 still minting coins, two gauges disagreeing, and a crossed-out kill switch

That was enough.

What was taken

At 12:26 UTC, block 25,315,715, attacker address 0x0f18…edd17 executed a single transaction and pulled:

  • 909 ETH (about $1.56M)
  • 270,513 DAI
  • 168 wstETH (about $357K)
  • plus yvDAI, yvWETH, LUSD and yvLUSD positions

Total: roughly $2.19M.

One transaction. No front-running, no flash loan, no governance takeover. A single call to a function that was supposed to settle zero-knowledge rollups.

The mismatch at the heart of it

The function was processRollup(), which verifies a ZK proof and settles the resulting state on L1. Two pieces of code participate: the verifier, which checks the proof, and the settlement logic, which acts on the data the proof covers.

They read the same data field differently. Specifically, numRealTxs.

The attacker crafted a rollup proof that satisfied the verifier but meant something different to the settlement code. The verifier said the proof was valid. The settlement code credited balances that did not exist. Those fabricated balances were then withdrawn.

This is the subtle class of failure worth paying attention to. Nobody broke the cryptography. The proof was valid. The bug was in the interface between "I have verified this" and "here is what the verified thing says", which is a place most ZK systems test far less than the proof itself.

The immutability paradox

Here is the part that should change how people think about shutdowns.

Aztec Labs relinquished all admin control in 2024. The contract cannot be paused, upgraded, modified or reversed. That was the point. Immutability is the property that makes on-chain systems trustworthy: no operator, including the original team, can change the rules after the fact.

The same property makes a deprecated contract with real assets inside an unstoppable attack surface. There is no kill switch. No emergency brake. No recovery path. The team that wrote it has no more authority to intervene than a stranger does.

"Can't be rugged" and "can't be fixed" are the same sentence read from different ends.

This was not a one-off

In a single week in June 2026:

  • Aztec Connect: $2.19M, contract deprecated three years earlier.
  • Raydium AMM V3: $1.34M, from legacy pools left over after a 2021 migration.
  • Hyperbridge: $2.5M, cross-chain bridge.
  • Syscoin Bridge: $8M, via a mint of 5 billion SYS.

Four incidents, one week, one pattern: attackers are systematically scanning abandoned contracts that still hold value. This is not opportunistic. It is a search strategy, and the search space is finite and public.

Every dead protocol on Etherscan is a row in someone's dataset, sorted by current balance.

The attacker was not improvising

The wallet was funded through Tornado Cash. The exploit used 14 batched rollup IDs, from 13277 to 13290. The whole thing was one carefully constructed transaction.

That profile tells you the amount of preparation involved. Someone found the contract, read both sides of the verification boundary, identified the interpretation gap, pre-funded an address for anonymity, and executed once. There was no second attempt because there did not need to be one.

What this means if you have ever shut something down

Deprecation is not death. A contract that has been "retired" is still a contract, and on most chains it stays executable forever.

The practical checklist for any team that has migrated, sunsetted, or abandoned a deployment:

1. Move the funds before you surrender the keys.
The order matters enormously. If admin control is relinquished while assets remain, you have created an unkillable vault with no owner and a known combination.

2. Assume your legacy contracts are being scanned.
They are in a public database with a balance column. The only question is whether the balance is worth someone's afternoon.

3. Treat "can't be paused" as an argument for emptying, not for confidence.
Immutability protects users from operator abuse. It does not protect them from a bug that was already shipped.

4. Audit the seams, not just the proofs.
Every place where a verified result is interpreted by other code is an attack surface. ZK verification is a particularly sharp example, because teams pour effort into the circuit and comparatively little into the binding between verifier output and settlement input.

5. Write down what your dead things are.
A list of deprecated contracts, their addresses, their balances, and who, if anyone, can still act on them. Most teams have a list of live deployments and nothing else.

The line to remember

Immutability is a property you buy once, and it applies to your mistakes as faithfully as to your guarantees.

Aztec Connect's contract did exactly what it was designed to do. It is still doing it. That is precisely the problem.

The archive: 61 investigations, 64 leak scans, 0 exploited

The archive. 61 on-chain investigations and 64 days of GitHub leak scanning, redacted and never used. Read the index or try the free token risk check at qanzhi111.github.io.

📰 Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.