Zilliqa moved fast after ZIL was stolen from a partner cold wallet, but the key number is still missing: how much was taken.
Zilliqa's July 20 disclosure gave the market one hard fact and several unanswered questions. ZIL had been stolen from a cold wallet tied to an exchange partner, and the project asked centralized exchanges to pause deposits and withdrawals so the tokens couldn't be moved or sold through their platforms.
That was the right first move. It was also a loud one.
Bitget said it would suspend ZIL deposits and withdrawals from July 20 at 18:15 UTC+8, citing wallet maintenance. Bithumb posted its own ZIL deposit and withdrawal pause at 6:50 p.m. Korea time because of suspected security concerns. Bitvavo said it had paused ZIL transfers as a precaution and added one useful detail: the incident did not involve a Bitvavo cold wallet.
If you hold ZIL, those exchange notices matter because they show the freeze was not just talk from the issuer. Real venues acted on it, and trading continued while transfers were restricted. That's awkward for anyone trying to price the token, because you can still sell exposure but you can't always move the asset cleanly.
The Missing Number Is Still The Problem
According to Zilliqa's statement, the project is working with the relevant parties to establish the root cause and full scope of the breach. ForkLog and other crypto outlets reported the same basic facts on July 20: the partner was unnamed, the amount stolen was undisclosed, and exchanges were asked to halt ZIL deposits and withdrawals temporarily.
Here's the thing. That isn't enough.
Zilliqa has not named the affected exchange partner. It has not said how much ZIL left the wallet. It has not said whether customers at the partner exchange face any loss. Those are not cosmetic details. They are the difference between a contained incident and a market-wide confidence problem.
The price move showed that traders understood the gap. CoinMarketCap's July 21 price analysis said ZIL was down 4.24% over 24 hours to $0.00246, after the security incident drove a coin-specific sell-off while the broader crypto market was rising. Cryptopolitan reported that ZIL touched $0.002441 on July 20, an all-time low, and that 24-hour volume jumped sharply as the market tried to process the news.
That is what uncertainty costs.
The Story Shifted After The First Freeze
The first version of this story looked like a straight partner custody breach. Then Zilliqa added a more important technical clue. As The Crypto Times noted in a July 21 update, Zilliqa said it had found no evidence, at that stage, that the incident was caused by the exchange's wallet management or operational processes. The project instead pointed to a technical issue affecting transaction signing in a specific set of legacy ZIL1 wallets.
That changes the shape of the risk. A bad custody process at one partner is one problem. A transaction-signing issue affecting a class of legacy wallets is broader and more uncomfortable, even if the final post-mortem narrows it later.
You don't need to overstate it. Zilliqa has not said the main network failed, and the exchange pauses affect deposits and withdrawals rather than normal on-chain ownership of self-custodied ZIL. But if a signing issue is involved, holders and exchanges need more than a calm sentence about an active investigation. They need the affected wallet type, the mitigation steps, and the number.
A cold wallet is supposed to be the safe option, kept offline so it can't be reached like a hot wallet sitting near exchange systems. When cold storage is drained anyway, the weak point is usually around access, signing, key handling, or procedure. In this case, Zilliqa's own update makes signing the part to watch.
Frankly, that is the whole story now.
The wider backdrop is not kind to Zilliqa either. CertiK's Hack3D H1 2026 report said Web3 projects lost more than $1.31 billion across 344 security incidents in the first half of the year, with wallet compromise the costliest attack vector at more than $444 million across 33 incidents. CertiK also said the Kelp DAO RPC compromise and Drift Protocol breach, both in April, together accounted for roughly 44% of H1 losses.
Those numbers don't prove anything about Zilliqa's breach. They do show why the market has little patience for vague security updates. Wallet and signing failures are where a lot of this year's biggest crypto losses have lived.
Zilliqa did the necessary thing: it told exchanges to slow the stolen tokens down. That's the easy part. The harder part is publishing the facts that let holders judge the damage - who the partner is, how much ZIL went missing, how far the signing problem actually spreads. Until it does, this stays an open incident: a token at depressed levels, and exchanges sitting on their hands, waiting for the next verified update.
Also read: Grayscale Files First US ETF for Sam Altman's Worldcoin After a 97% Crash, Cardano's Van Rossem Hard Fork Proves Community Voting Can Run a Blockchain, and South Korea Opens a Formal Sanctions Case Against Upbit's Parent Dunamu
