Milk Sad

CVE-2023-39910: Libbitcoin Explorer 3.x bx seed used a Mersenne Twister PRNG seeded by 32-bit system time. A wallet made that way had about 4.3 billion possible keys instead of 2256.

CVE-2023-39910Weak entropyOwner action

What happened

bx seed in libbitcoin-explorer 3.x generated key material with MT19937. Seeding that generator with a 32-bit timestamp collapsed the key space to roughly 232. Any wallet created with affected bx seed versions can be reproduced by anyone who guesses the generation time.

The vulnerability is public and documented by the Milk Sad project. It is not a flaw in Bitcoin, secp256k1 or the wallets that generate keys from a proper CSPRNG.

Audit a known 32-bit seed

bx seed seeded MT19937 with the low 32 bits of the high-resolution clock. This form reproduces one published seed value; it is an owner audit for a seed you already have, not a scan of other people's keys. Seed 0 reproduces the public Milk Sad test vector.

Check your address against a seed range

Enter a Bitcoin address you control, a seed range and scan locally. The page recovers a key only when your address matches; it never lists other wallets and never checks balances.

Browse the 232 seed space

Every 32-bit seed produces one bx-seed wallet. This is the same key calculator as the rest of Crypto, limited to that 232 set and computed locally. No balances are looked up here; open a derived address in an explorer if you need to check it.

seeds 0…59

Are you affected?

Use the official checker and the published research to evaluate a specific wallet: milksad.info. Do not paste a live seed phrase into an arbitrary site; use an offline machine for a real wallet.

What to do

  1. Create a new wallet with a reputable CSPRNG and a fresh seed phrase.
  2. Move the funds to the new wallet as soon as you can, starting with the highest-value addresses.
  3. Do not reuse the old seed phrase, even after moving the funds.
  4. If the key is still online, treat it as public: an idle vulnerable key cannot be protected by watching it.

This page is documentation, not a recovery service. Crypto does not scan third-party wallets, does not hold funds and cannot move them for you.

Why this page does not list vulnerable keys

A searchable directory of every weak key and its balances is a target list, not a safety tool. It helps someone take funds from wallets they do not own. The owner of an affected wallet already has the public research and the official checker; publishing the whole enumeration adds no protection for that owner.