Original source text
A bug that sat quietly in Zilliqa’s Ledger hardware wallet app for seven years just went from dormant to devastating. The flaw, present in every version of the app since its 2019 launch, allowed attackers to recover users’ private keys from publicly available on-chain data.Zilliqa detected active exploitation on July 19, 2026. Two days later, the team isolated the root cause and immediately suspended all native ZIL transactions.
What went wrong, and for how long The vulnerability lives in how the Ledger app generates nonces for EC-Schnorr signatures during native ZIL transactions. The most significant 64 bits of the ephemeral nonce were fixed at zero, stemming from a mishandling of a 32-byte copy from a 40-byte randomness buffer.
Advertisement
That partial predictability is a death sentence for cryptographic security. An attacker with access to just five or more affected signatures, all of which are visible on-chain to anyone who cares to look, could use a technique called lattice reduction to mathematically reverse-engineer a user’s private key.
This is not a flaw in Zilliqa’s blockchain itself, nor in Ledger’s core hardware security. It’s a bug in the companion app, the software layer that connects the Ledger device to the Zilliqa network. Zilliqa’s SDKs, including zilliqa-js, gozilliqa-sdk, and pyzil, remain completely unaffected. EVM-compatible transactions processed through the Ledger are also fine, since those use a different signing routine.
The fallout so far Upbit, one of the largest crypto exchanges in South Korea, designated ZIL as a cautionary asset and halted both deposits and withdrawals. Other exchanges are reportedly monitoring the situation.
Zilliqa’s response has been a mix of crisis management and damage control. The team confirmed the root cause was isolated on July 21, and they are now collaborating directly with Ledger to develop a fix.
The company has been explicit in its guidance to affected users. Compromised keys need to be retired entirely, not transferred. If an attacker has already derived your private key, they can front-run any transfer you attempt. The recommended path is to generate entirely new keys through a secure method and treat the old ones as permanently burned.
What investors should watch The immediate concern for ZIL holders is whether the suspension of native transactions will be brief or prolonged. A fix requires coordination between Zilliqa and Ledger. Until a patched app is released, audited, and verified, native transactions will likely remain frozen. With Upbit already halting deposits and withdrawals, trading volumes for ZIL are under pressure from multiple directions simultaneously.
For anyone holding ZIL on a Ledger device, the priority is straightforward: do not attempt to move funds using the compromised app. Wait for official guidance from Zilliqa on the key retirement process.
Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our Editorial Policy.