Analysis of the $2.19 Million Asset Theft from Aztec Connect

Incident Overview

On June 14, 2026, the Aztec Connect RollupProcessor contract was exploited, resulting in the theft of around $2.19 million worth of assets. The attack exploited a vulnerability in the contract's design, specifically a gap between the Layer 1 (L1) and Layer 2 (L2) state verification processes.

Details of the Exploit

The vulnerability arose from a structural gap between the number of real transactions (numRealTxs) and the decoded slots in the rollup settlement process. The attacker was able to manipulate this gap, allowing them to extract assets without proper verification at the L1 contract layer.

The attack involved a single atomic transaction that included 14 processRollup() calls. The attacker first minted assets on L2 by exploiting the gap slots, which were not verified by the L1 layer. Subsequently, they withdrew these inflated balances into L1 assets, successfully transferring a total of $2.19 million.

On-Chain Evidence

According to on-chain forensic tracking, all stolen assets were transferred to the attacker's externally owned account (EOA) within a single transaction. As of June 15, 2026, the stolen funds remained intact and had not yet been laundered.

The attacker's EOA, identified as 0x0F18D8b44a740272f0be4d08338d2b165b7EdD17, received various assets, including DAI, wstETH, and ETH, among others. The intermediate contract used in the attack held no remaining funds, indicating a clean exit for the attacker.

Implications and Recommendations

This incident highlights critical vulnerabilities in the design of ZK-Rollup systems. The gap between the L1 settlement loop and the ZK public input hash must be addressed to prevent similar exploits. Security assumptions that rely solely on ZK circuit constraints can be bypassed if not independently verified at the L1 layer.

SlowMist recommends that blockchain projects conduct comprehensive external security audits, particularly focusing on the logical consistency at the L1/L2 state boundary. For deprecated contracts holding legacy assets, it is advisable to migrate or destroy these assets to mitigate ongoing risks.