Zilliqa has halted native ZIL transactions following the invention of a vital vulnerability within the community’s Ledger utility, which permits the personal keys of sure accounts to be recovered from public signatures on the blockchain. The incident was disclosed after an undisclosed quantity of ZIL was stolen from an trade companion’s chilly pockets, forcing the venture to request centralized platforms to pause ZIL deposits and withdrawals to curb the motion of funds.
Based on Zilliqa, the flaw lies within the native transaction signing course of utilizing the Ledger app and doesn’t have an effect on EVM transactions or official SDKs. The venture acknowledged that the vulnerability had existed in app variations courting again to 2019, with on-chain exploitation indicators detected on July 19, 2026, two days earlier than the basis trigger was remoted.
Change Theft and Preliminary Response
Zilliqa publicly disclosed the incident on July 20, stating that an undisclosed quantity of ZIL had been stolen from an trade companion’s chilly pockets. On the time, the venture didn’t specify the technical trigger or the size of damages, noting that an investigation was ongoing to find out the basis trigger and the scope of impression.
Now we have been made conscious of a safety incident involving one in all our trade companions, during which ZIL was stolen from a chilly pockets.
The incident is underneath energetic investigation, and we’re working with the related events to ascertain the basis trigger and full scope. As a…
— Zilliqa (@zilliqa) July 20, 2026
Exchanges had been subsequently notified and requested to pause ZIL deposits and withdrawals as a precautionary measure to stop the stolen funds from being transferred or bought via centralized platforms whereas the verification course of continued.
On July 21, Zilliqa up to date that it discovered no proof suggesting the incident originated from pockets administration procedures or operational actions of the trade. The investigation then shifted to a technical subject affecting transaction signing in a bunch of legacy ZIL1 wallets, earlier than the venture disclosed detailed details about the vulnerability within the Zilliqa Ledger app a day later.
Affected Wallets and Transaction Scope
Zilliqa restricted the scope of impression to non-public keys that had been used to signal native Zilliqa transactions through a Ledger gadget. Based on the venture’s advisory, accounts which have broadcast roughly 5 or extra native transactions utilizing the Zilliqa Ledger app needs to be thought of compromised.
This threat applies to signatures already publicly recorded on-chain, which means subsequent software program updates can’t reverse the publicity degree of affected personal keys. Customers with accounts on this group should cease utilizing the compromised keys, relatively than merely updating the transaction-signing app.
EVM transactions are unaffected, whereas transactions signed via official SDKs resembling zilliqa-js, gozilliqa-sdk, and pyzil are additionally outdoors the scope of the flaw. The incident is subsequently remoted to the native signing path of the Zilliqa Ledger app.
Zilliqa has not disclosed the quantity of ZIL stolen, the variety of affected accounts, or the overall worth of belongings held in weak addresses. In consequence, the general monetary extent of the incident stays unclear.
Ledger App Vulnerability
The foundation trigger lies in how the Zilliqa Ledger app generates nonces for EC-Schnorr signatures on the secp256k1 curve. For every signature, the app must generate a contemporary, random, and unpredictable 256-bit nonce; if the nonce is biased or lacks entropy, a number of signatures can expose the personal key.
The app’s signing routine generates 40 bytes of randomness after which reduces this worth modulo the order of the curve to provide a 256-bit quantity. Nevertheless, when copying the end result into the nonce buffer, the code mistakenly extracted 32 bytes from the 40-byte output, retaining 8 bytes of zero-padding whereas discarding 8 bytes of entropy.
This flaw leaves the 64 most vital bits of every nonce fastened at zero. With roughly 5 or extra affected signatures, the personal key may be recovered in seconds on commodity {hardware} utilizing Hidden Quantity Downside fixing and lattice discount strategies.
Native Transaction Halt
Zilliqa halted native non-EVM transactions as a protecting measure whereas finalizing a remediation plan. The transfer goals to stop additional asset losses from weak accounts whereas limiting the motion of stolen ZIL via the native transaction movement.
Affected accounts can’t be protected by a normal switch transaction both. If a non-public key can already be recovered from on-chain information, an attacker holding the identical key can detect and front-run the consumer’s asset switch transaction. Subsequently, making an attempt to maneuver funds independently could also be ineffective and improve threat, whereas EVM transactions proceed to stay unaffected.
Remediation Plan and Consumer Steerage
A hard and fast construct of the Ledger app is being ready in coordination with Ledger. This repair will restore the total nonce era course of to stop the app from creating additional weakened signatures sooner or later. Nevertheless, the patch can’t reverse the danger for personal keys which have already signed the required variety of affected native transactions beforehand.
Keys belonging to the affected group in the end have to be retired from use. Zilliqa is finalizing a remediation plan to safeguard balances in related accounts and can publish separate directions for customers who’ve signed native Zilliqa transactions utilizing Ledger. Till official steerage is supplied, customers are suggested to not act independently and to observe solely the venture’s official channels.
KuCoin was credited by Zilliqa for aiding in figuring out the basis trigger throughout the Ledger app’s nonce era course of, recovering affected personal keys from on-chain information, and confirming ongoing exploitation exercise. Nevertheless, Zilliqa has not publicly confirmed whether or not KuCoin was the trade companion that misplaced ZIL within the preliminary announcement.
