Zilliqa Ledger application has a vulnerability, and the private keys used to sign 5 or more transactions are at risk of being restored

Zilliqa has revealed a random number generation vulnerability in its Ledger application, which poses a risk of restoring the private keys of 5 or more native transactions signed between 2019 and 2026. This vulnerability is due to the fact that the maximum 64 bits of the random number are fixed to zero, resulting in insufficient entropy value. Attackers can use on chain data to restore the private key. Zilliqa has temporarily suspended native trading and recommends users to wait for official guidance and not take independent action at this time. EVM transactions and related SDKs are not affected.