How a Deprecated Aztec Contract Lost $2.1M Three Years After Shutdown

A dormant, deprecated smart contract on Ethereum has become the latest cautionary tale for decentralized finance. On June 14, 2026, an attacker siphoned approximately $2.1 million in crypto assets from Aztec Connect, a privacy-focused ZK-rollup bridge that the Aztec Labs team had shut down in March 2023 . The breach was not the result of a live product vulnerability, but rather a flaw in an abandoned contract that had been deliberately stripped of all administrative control, leaving it forever frozen—and forever vulnerable.

Security firm CertiK first flagged suspicious activity from the RollupProcessorV3 contract, the core router for Aztec Connect's deprecated rollup, with the attacker's wallet identified as 0x0f18d8b44a740272f0be4d08338d2b165b7edd17 . The total loss was pegged at roughly $2.19 million by CertiK, while Aztec Labs cited a figure closer to $2.1 million . The stolen assets included about 909 ETH, 270,000 DAI, 167 wstETH, and additional Yearn vault tokens such as yvDAI, yvWETH, and yvLUSD .

How the attacker bypassed ZK-rollup verification

The exploit targeted the boundary between the zero-knowledge proof verification logic and the settlement processing on Ethereum's Layer 1. According to CertiK, one of the contract's verification functions only checked the beginning of a submitted proof, meaning the parameters used to authorize token transfers were never fully validated . This allowed the attacker to submit a proof that passed initial checks while containing malicious withdrawal instructions deeper in the data payload.

SlowMist's subsequent analysis identified a root cause in the traversal limits of the L1 settlement loop within RollupV3. The attacker exploited a discrepancy between numRealTxs and decoded_slots, enabling the submission of 31 empty slots to the L2 state root via a ZK proof while sidestepping full verification at the L1 contract layer . The attacker ultimately constructed 14 ZK-rollup proofs; the final seven proofs each drained a different asset from the contract in separate transactions .

A deliberate renunciation of control

What makes this incident unique is that the attack was structurally unstoppable—by design. Aztec Connect was deprecated in March 2023, and users were given over a year to withdraw their funds . In 2024, Aztec Labs went further, deliberately surrendering all admin keys and control over the system. The contracts became fully immutable: no upgrade mechanism, no owner, and critically, no pause function .

“Aztec Connect was deprecated 3 years ago. Aztec Labs holds no admin keys or control over the system; it cannot be paused or upgraded,” the team stated on X hours after the exploit, confirming roughly $2.1 million had moved from the immutable contract . They emphasized that the current Aztec Network and its AZTEC ERC-20 token were not affected, but acknowledged there was no mechanism to recover the lost funds .

Despite the extended withdrawal window and communication around the shutdown, approximately $2.1 million in residual user assets remained locked inside the old contracts at the time of the attack . The funds existed in a kind of limbo: no one could retrieve them legitimately without interacting with the deprecated rollup, and no one could intervene when the vulnerability was triggered.

The broader risk: zombie contracts in DeFi

The Aztec Connect exploit is a textbook illustration of the "zombie contract" problem in decentralized finance. Immutable smart contracts do not simply fade away when a project shuts down. They persist on-chain with whatever logic—and value—they contain, often retaining user assets indefinitely. When admin keys are renounced in pursuit of full decentralization, the contract becomes a permanent, unpatchable honeypot. Any undiscovered vulnerability becomes a time bomb that can be detonated years later with zero recourse .

This risk is asymmetric. Projects that renounce control earn credibility for having no backdoor, but users who fail to withdraw during deprecation windows bear the full downside. The Aztec case shows that even after three years, millions of dollars can remain trapped in a contract everyone assumed was dead.

For DeFi teams planning to deprecate a protocol, the lesson is stark. Before renouncing admin keys, projects must either force-complete all withdrawals or implement a timelock-based emergency mechanism that does not require long-term admin control. Without those safeguards, abandoned but immutable infrastructure will inevitably attract attackers willing to search for flaws that can never be fixed .