A critical bug in Zilliqa's Ledger hardware wallet app exposed thousands of user keys, enabling attackers to steal over 683 million ZIL. The incident highlights persistent risks in wallet software and the challenges of securing legacy blockchain infrastructure.
A major vulnerability in Zilliqa's Ledger hardware wallet application has resulted in the exposure of at least 6,772 user accounts and the confirmed theft of 683,130,969.66 ZIL tokens, according to a post-mortem published by Zilliqa. The flaw, which affected the legacy signing path of the Ledger app, allowed attackers to reconstruct private keys from public blockchain data, putting user funds at immediate risk and forcing the project to halt legacy transactions while it works on a migration plan.
How the Flaw Was Introduced
The vulnerability stemmed from a coding error in the Zilliqa Ledger application's random number generation process. Instead of copying 32 bytes of true entropy into the signing buffer, the application mistakenly included eight bytes of zero padding and discarded eight bytes of randomness. This forced the high 64 bits of every affected nonce to zero, creating a predictable pattern in transaction signatures. With as few as four biased signatures from the same account, attackers could reconstruct the private key using only public blockchain data and ordinary hardware. Zilliqa's analysis found that at least 6,772 accounts were mathematically exposed, with 51 accounts confirmed to have been drained in the attack window.
Scope of the Incident and Response
The attack was first traced to March 4, with the last known malicious transaction occurring on July 20 at 09:19:09 UTC. Zilliqa disabled legacy transactions later that day to prevent further losses. The project's post-mortem distinguishes between the total number of exposed accounts and those that were actually drained, noting that the 6,772 figure is a lower bound and could rise if more compromised accounts are identified. The 683.13 million ZIL loss is based on currently known thefts, but the total could increase as investigations continue. Zilliqa has not yet quantified the number of affected individuals, as some addresses may be controlled by the same user or entity.
Migration and Recovery Plans
Zilliqa has announced that all legacy wallet holders will be required to migrate to the Zilliqa EVM (Ethereum Virtual Machine) environment, with the legacy signing path set for retirement. The timing of the migration tool's launch remains uncertain, as it depends on the completion of an external security audit and any necessary remediation. In the meantime, asset tracing and coordination with exchanges are ongoing. The vulnerability does not affect Zilliqa EVM activity, recovery phrases, or assets held on other blockchains via the same Ledger device. Only the legacy, non-EVM signing path is impacted.
Industry Context and Security Lessons
The Zilliqa Ledger incident underscores the persistent risks associated with hardware wallet software and the challenges of maintaining secure cryptographic implementations over time. The flaw survived years of maintenance by both Zilliqa and Ledger without detection, highlighting the need for rigorous code review and independent security audits. Similar concerns have been raised in other blockchain ecosystems, such as the push to close cryptographic proof gaps in Ethereum's zkEVM security, as discussed in recent coverage of Ethereum's ongoing security upgrades.
According to Zilliqa's published figures, the 683,130,969.66 ZIL stolen in the incident represents a significant portion of the network's circulating supply. As of July 20, 2026, Zilliqa's total circulating supply was approximately 17.5 billion ZIL, meaning the theft accounted for nearly 4% of all tokens in circulation. The incident affected at least 6,772 accounts, with 51 confirmed to have been drained, and forced the suspension of legacy transactions network-wide.
Hardware wallets are widely regarded as one of the most secure ways to store cryptocurrency, but their safety ultimately depends on the integrity of both device firmware and wallet application code. Even small implementation errors in cryptographic routines can have catastrophic consequences, as demonstrated by the Zilliqa Ledger bug. Users should be aware that correcting a vulnerability in wallet software can protect new keys, but cannot retroactively secure keys that have already been exposed through compromised signatures. Regular security audits, prompt incident disclosure, and transparent migration processes are essential for maintaining user trust in self-custody solutions.
