Security researchers are sounding the alarm after a critical vulnerability in a widely used Bitcoin development library was confirmed to expose over 120,000 wallets to brute-force attacks. The flaw, embedded in the Libbitcoin Explorer (bx) 3.x library, exploits a fundamental weakness in how random numbers are generated during wallet creation — and it has been hiding in plain sight since November 2023.
On October 17, 2025, the OneKey wallet team publicly disclosed the technical details of the vulnerability, which traces its origins to the so-called “Milk Sad” incident. While the bug was identified two years ago, the sheer number of wallets still at risk has reignited concerns across the cryptocurrency security community. With Bitcoin trading above $106,000 at the time of disclosure, the potential losses from this vulnerability could be catastrophic.
The Exploit Mechanics
At the heart of the vulnerability lies a deceptively simple programming flaw. The Libbitcoin Explorer 3.x library relied on the Mersenne Twister-32 algorithm to generate random numbers during the wallet seed creation process. This algorithm, while efficient for many applications, was seeded exclusively by the system time — a dramatically insufficient entropy source for cryptographic purposes.
The result? The entire seed space was constrained to just 2³² possible values — approximately 4.3 billion combinations. For a high-performance computer, enumerating every possible seed takes only days. Once an attacker knows the approximate time a wallet was generated, they can narrow the search space even further and derive private keys in a matter of hours.
The vulnerability specifically affects wallets that were generated using Libbitcoin Explorer 3.x directly, as well as certain legacy versions of Trust Wallet that relied on the same library for key generation. The OneKey team confirmed that their own hardware and software wallets are not affected, as they use different cryptographic libraries for seed generation.
Affected Systems
The scope of the vulnerability is staggering. Researchers have identified more than 120,000 Bitcoin addresses that were generated using the compromised random number generation process. These wallets span multiple platforms and services that integrated Libbitcoin Explorer as a dependency, including several early mobile wallet applications and command-line tools popular among developers.
What makes this vulnerability particularly insidious is its silent nature. Wallets created with the flawed library appear to function normally — transactions process, balances display correctly, and the user experience is indistinguishable from a properly secured wallet. The weakness exists solely in the mathematical predictability of the underlying seed generation, invisible to anyone not specifically analyzing the entropy source.
The timing of the disclosure coincides with Bitcoin’s sustained presence above the $100,000 mark, making these vulnerable wallets potentially high-value targets. Ethereum, trading at approximately $3,832 on the same date, and other major cryptocurrencies like Solana at $182 and BNB at $1,071, remain unaffected by this specific vulnerability.
The Mitigation Strategy
For users who suspect their wallets may have been generated using Libbitcoin Explorer 3.x, security experts recommend a three-step remediation process. First, immediately transfer all funds from the potentially compromised wallet to a newly created wallet using a modern, audited wallet application that employs robust entropy sources such as hardware random number generators or operating system-level CSPRNGs.
Second, verify the provenance of your wallet’s seed generation. If you used a command-line tool or older mobile application to create your wallet between 2017 and 2023, there is a higher probability that the Libbitcoin library was involved. Documentation for most wallet providers indicates which cryptographic libraries they use for key generation.
Third, adopt hardware wallets for long-term storage. Devices from manufacturers like OneKey, Ledger, and Trezor generate entropy using dedicated secure elements that are fundamentally resistant to the type of predictable RNG attack that compromised the Libbitcoin library.
Lessons Learned
The Libbitcoin vulnerability serves as a stark reminder that the security of cryptocurrency holdings depends not just on the strength of encryption algorithms, but on the quality of every component in the software stack. A single weak random number generator, buried deep in a dependency, can undermine the entire security model of a wallet.
The incident also highlights the importance of responsible disclosure timelines. While the vulnerability was first identified in late 2023, the two-year gap before widespread public awareness has left hundreds of thousands of wallets exposed. The cryptocurrency industry must develop faster, more comprehensive vulnerability notification systems to protect users.
Open-source library maintainers bear a shared responsibility. The Libbitcoin project has since patched the RNG vulnerability in newer versions, but the long tail of dependent applications and user-generated wallets means the threat persists indefinitely for those who have not migrated their funds.
User Action Required
If you generated a Bitcoin wallet using Libbitcoin Explorer 3.x, Trust Wallet legacy versions, or any tool that relied on the Libbitcoin C++ library for key generation, take immediate action. Move your funds to a new wallet generated with a modern application, verify that your new wallet uses a recognized CSPRNG, and store your seed phrase securely offline. Do not delay — the vulnerability is publicly known and actively exploitable.
Disclaimer: This article is for informational purposes only and does not constitute financial or security advice. Always consult with qualified security professionals regarding the protection of your digital assets.
Mersenne Twister for wallet seeds in 2023 is wild. every CS freshman learns this is not crypto-safe in semester one
seeding a crypto wallet RNG with system time only. 2 to the 32 possible values. a modern GPU can brute force that in hours. this is a textbook failure
entropy max seeding with system time means 2 to the 32 possibilities. a single RTX 4090 can enumerate that in under a day. this is not a vulnerability its a backdoor by incompetence
rng_audit_ exactly. 2^32 seed space and a single GPU enumerates it in hours. this was known since the 90s, using MT for keys is negligence
120K wallets exposed since November 2023 and the disclosure came in October 2025. two years of wallets that could be brute forced at any moment. the response time is the real scandal
OneKey disclosing it publicly in Oct 2025 when wallets were vulnerable since Nov 2023. how many people got silently drained in between
The fundamental value proposition of crypto keeps getting stronger
Every cycle the infrastructure gets more robust
Hana Suzuki robust infrastructure didnt help 120000 wallets generated by Libbitcoin Explorer. the bug was there since November 2023 and nobody caught it for two years
The gap between crypto and TradFi is narrowing fast