zkLink Nova suffered a cross-chain bridge exploit that enabled an attacker to withdraw approximately $783,100 in cryptocurrency from Ethereum escrow contracts by manipulating the system’s withdrawal verification process. The incident involved a publicly callable relayer and a reported validation flaw in the protocol’s Arbitrator contract, allowing unauthorized withdrawals of ETH and 11 other tokens.
The first identified transaction occurred at 22:21:35 UTC on October 28, equivalent to 01:21:35 Cairo time on October 29. A second withdrawal transaction was subsequently identified at approximately 01:43 UTC on October 29. The attacker converted the initially extracted assets into approximately 303 ETH and 32,157.74 DAI before distributing funds to three addresses.
On October 29, zkLink confirmed that the exploit was ongoing and that its technical team was working to contain the incident. The project offered a 20% white-hat bounty in exchange for the return of the affected funds, while warning that the attack targeted zkLink Nova’s Arbitrator contracts on Ethereum and Optimism.
Forged withdrawal roots enabled unauthorized asset releases
The incident centered on the mechanism that validates withdrawals from zkLink Nova, a blockchain network whose bridge infrastructure relies on cross-chain messages and cryptographic proofs to authorize asset transfers.
Under normal conditions, a withdrawal from a rollup to Ethereum must be supported by valid information establishing that the transaction was authorized on the originating network. The bridge’s verification process is intended to prevent someone from inventing a withdrawal and using it to release assets held in Ethereum contracts.
According to SlowMist’s technical description of the incident, the attacker exploited the interaction between the publicly callable SyncL2TxHashRelayer and a flaw in the Arbitrator contract. The reported weakness involved the failure to clear a temporary message hash, known as finalizeMessageHash, after use, alongside inadequate authentication requirements for subsequent calls.
The described sequence allowed the attacker to populate a valid message hash and then reuse it while introducing an attacker-controlled l2LogsRootHashes root under the identity of the legitimate gateway. Once that forged root had been accepted, the attacker could submit withdrawal proofs that appeared valid against the manipulated root.
This distinction is important. The reported attack did not simply involve stealing a private key or exploiting a price discrepancy. It targeted the process that determines whether the bridge should release assets in the first place. If the verification mechanism accepts a fraudulent representation of authorized activity, the escrow can release real assets against withdrawals that were never legitimately approved.
However, zkLink has not published a definitive root-cause report confirming the complete technical sequence. SlowMist’s description should therefore be treated as a security analysis rather than a final finding formally endorsed by the project.
On-chain movements reveal two identified withdrawal transactions
The first identified drain took place on Ethereum at 22:21:35 UTC on October 28. The transaction removed approximately 22.43 ETH from the ETH escrow and transferred 11 different ERC-20 tokens from the bridge contract to the receiving wallet.
The receiving wallet subsequently exchanged the extracted assets, producing approximately 303 ETH and 32,157.74 DAI before funds were distributed to three addresses. These movements provide a traceable picture of how the initial proceeds were consolidated and transferred, although they do not establish the identity of the individuals controlling the destination wallets.
A second withdrawal transaction was identified at approximately 01:43 UTC on October 29, or 04:43 in Cairo. Available transaction reporting indicates further token outflows from the bridge, including a substantial quantity of ZKL and additional smaller token balances. This expanded the scope of the identified activity beyond the first withdrawal.
SlowMist estimated the identified losses at approximately $783,100. Other early estimates differed, reflecting variations in asset pricing and the timing of the assessments. The figure should not be interpreted as an audited final loss total, particularly because zkLink described the exploit as ongoing in its initial public disclosure.
The incident resembles other recent bridge security failures, including the Payy Ethereum bridge exploit, which drained approximately $1.83 million in USDC and forced the payments platform to halt several services. The incidents involve different systems and should not be treated as technically equivalent, but both demonstrate how a weakness in bridge infrastructure can expose assets held in on-chain contracts.
zkLink offers a 20% bounty as the investigation continues
At 09:06:04 UTC on October 29, equivalent to 12:06:04 Cairo time, zkLink publicly acknowledged an ongoing exploit targeting its Arbitrator contracts on Ethereum and Optimism. The team said it was working urgently to contain the situation and prevent further damage.
The project called on the attacker to stop exploiting its cross-chain contracts and return the affected funds. It offered a 20% white-hat bounty in exchange for cooperation, stating that it would not pursue further action if the funds were returned under the proposed arrangement.
The offer creates a potential recovery route, but it does not guarantee that the attacker will cooperate or that any assets will be returned. Nor does the public disclosure establish the extent of the exposure across every affected network. The confirmed withdrawal activity and the project’s warning about both Ethereum and Optimism must be distinguished from a comprehensive accounting of all possible losses.
In its official exploit announcement, zkLink did not provide a definitive technical post-mortem or a final accounting of the losses. The project’s initial response therefore leaves important questions about containment, contract security and recovery unanswered.
Other bridge incidents show why the distinction between an initial loss estimate and the eventual financial outcome matters. In the Cysic bridge exploit, unauthorized issuance of 10 million CYS tokens raised questions about how much value was ultimately extracted and how much could be restricted or recovered. Token quantities, nominal market values and realized losses are not interchangeable measures.
Why the exploit matters beyond the immediate loss
The most consequential aspect of the zkLink incident is the reported failure in withdrawal authorization. A bridge’s security depends not only on protecting keys and preventing unauthorized contract calls, but also on ensuring that every accepted message and cryptographic proof corresponds to legitimate activity on the originating network.
A publicly callable relayer is not inherently unsafe. Permissionless infrastructure can be useful in decentralized systems, provided that downstream contracts independently verify the authenticity and integrity of the messages they receive. The concern in this case is the reported combination of an authorized relayer pathway, reusable transient state and insufficient authentication of subsequent calls.
If that technical description is confirmed, the vulnerability would raise questions about whether similar message-processing assumptions exist in other parts of the protocol. It would not, by itself, prove that every zkLink deployment or every bridge using comparable architecture is vulnerable. Establishing the scope requires code-level investigation, identification of affected contract versions and testing of the relevant validation paths.
The incident also illustrates why a relatively modest reported loss can have consequences beyond the amount stolen. Bridge users depend on the relationship between assets held in custody and the claims that can be redeemed on connected networks. When withdrawal verification is compromised, users may face uncertainty about whether the remaining escrow can satisfy legitimate withdrawal requests, even if the attack affects only a subset of assets.
The Symbiosis Bitcoin bridge exploit provides another example of why the number of tokens created or affected does not automatically determine the final economic loss. Recovery, liquidity, conversion opportunities and the amount of value that actually leaves the system all matter when assessing an incident’s financial consequences.
What users and investors should monitor next
The immediate priorities are confirmation that the exploit has been contained, a clear explanation of the vulnerability, and evidence that the relevant contracts have been secured against further unauthorized withdrawals. A credible post-mortem should explain how the forged root passed validation, why the temporary message hash was not safely cleared, and what changes have been implemented to prevent the same sequence from recurring.
Users should also look for explicit guidance from zkLink about affected networks, bridge availability and the treatment of outstanding withdrawal claims. The project’s initial announcement did not establish a final reimbursement plan or confirm the full extent of exposure on Optimism. Users should avoid relying on unofficial recovery offers or signing transactions presented as urgent compensation procedures.
For investors, the key question is whether the incident remains isolated or exposes a broader weakness in the protocol’s cross-chain verification design. A rapid technical fix may limit additional losses, but confidence will depend on the quality of the investigation, independent validation of the remediation and transparent communication about any remaining risks.
The approximately $783,100 estimate is therefore an important starting point, not the final measure of the incident. The first drain and subsequent withdrawal establish that assets were released through the affected bridge infrastructure, while the project’s own disclosure confirms that it was responding to an ongoing exploit. Until zkLink publishes a definitive root-cause analysis and a reconciled loss figure, the full scope of the breach, the prospects for recovery and the security of the affected withdrawal pathways remain unresolved.
Johan Shamshad is a financial markets writer at Dave Finances covering cryptocurrencies, trading platforms, brokers, fintech, financial regulation, and developments across global markets. He previously worked at Gulf News, adding newsroom experience to his coverage of fast-moving financial and digital-asset markets.
His work focuses on identifying market-moving events, company developments, regulatory changes, product launches, and shifts in trading and financial infrastructure.
Johan contributes news and analysis designed to help readers understand not only what happened, but why a development matters and how it may affect the wider financial landscape. You can reach out to him via his social media accounts:
Linkedin: https://www.linkedin.com/in/johan-shamshad-742851262/
X: https://x.com/Yasmine_FX
Investing: https://www.investing.com/members/contributors/279781574