Implementation errors and security risks in ZKsync account abstraction
Logic errors in the State Transition Manager and administrative vulnerabilities led to an exploit where 111 million ZK tokens were minted. These flaws impact chain management, fee predictability, and security during the transition to the Atlas upgrade and Elastic Chain interoperability.
The State Transition Manager (STM) contains logic errors that affect ZK Chain management. The unfreezeChain function incorrectly calls freezeDiamond, which triggers a revert and forces the State Transition Manager to rely on the chain admin to perform the unfreezing process for the ZK Chain. The STM owner holds the power to define how ZK Chains initialize and upgrade, including the ability to freeze and unfreeze specific chains. The BridgeHub creates new ZK Chains that the STM manages. The STM also sets the execution delay between committing and executing batches. Additionally, the setValidiumMode function in the Admin facet allows the admin role to toggle between Rollup and Validium modes. Because the changeFeeParams function also allows this mode to be set, administrators can change the mode after batches are committed. This ambiguity means users requesting L2 transactions through the Mailbox facet might face unpredictable L1 PubData charges.
Security vulnerabilities in administrative control caused a major exploit where an attacker used the sweepUnclaimed() function to mint 111 million ZK tokens. This breach occurred because a compromised administrator account controlled three separate airdrop distribution contracts. The resulting event caused the ZK token value to drop by over 15%. During the token launch, the Web3 security company Blockaid recorded a 5-fold increase in malicious dApps targeting ZKsync.
| Feature | Constraint or Consequence |
|---|---|
unfreezeChain |
Causes a revert via freezeDiamond |
setValidiumMode |
Can be changed via changeFeeParams |
sweepUnclaimed() |
Mints tokens via compromised admin key |
| AA Verification | Restricted access to block.timestamp |
Developers must navigate strict constraints during the account abstraction verification step to prevent DoS attacks. This process allows only a limited amount of ergs and restricts access to the storage of the wallet. The mempool limits the number of transactions from a single address to five. If the validation step fails, the operator returns all funds taken in the first step and exits. The operator also checks that the user has enough funds before the VM calls the validateTransaction method. For those of you already managing smart accounts, the lack of a unified EntryPoint makes deployment difficult. Current implementations often require an EOA to call a smart account factory, which forces the EOA to pay the deployment fees.
The migration of the Elastic Network to Ethereum L1 in early Q1 2026 allowed for the deployment of the Atlas upgrade, which includes the introduction of new components such as ZKsync OS and Airbender. During this phase, chains settled directly on L1 to facilitate the rollout of the next protocol upgrade. The Atlas update provides 15,000 transactions per second and one-second finality. Vitalik Buterin endorsed the Atlas upgrade, calling the team’s work underrated but valuable. This upgrade includes the P256Verify precompile to support biometric and hardware authorization. This precompile allows Dapps to accept Passkeys, Yubikey, Android Keystore, or Apple’s Secure Enclave. The P256Verify interface allows developers to integrate elliptic curve signatures into the ZKsync Zk Stack Elastic Chain easily. The 2026 roadmap also prioritizes the integration of Prividium with enterprise workflows. Will the P256Verify precompile eliminate the need for users to manage complex private keys?
Join the discussion