If a cryptocurrency wallet moved funds without your say-so in the past six weeks, the Ill Bloom vulnerability is a real candidate for why. Blockchain security firm Coinspect has linked more than $5 million in theft to a class of wallet apps. Those apps generated recovery phrases with weak, predictable randomness instead of the strong entropy the process demands. Here is what the bug does, who it hits, and how to check your own exposure.
What the Ill Bloom vulnerability breaks
A recovery phrase is a twelve or twenty-four word backup. It guards the whole wallet. It should come from an enormous space of possible combinations. Coinspect found that a handful of wallet implementations built that phrase using an insecure random number generator. Insecure generators produce output that looks random on the surface. In reality it is mathematically predictable once you know how the generator was seeded.
That predictability is fatal. Coinspect describes the intended phrase space as “trillions upon trillions” of combinations. An attacker who spots the pattern only has to search a small, computable range instead. Recovery phrases follow the BIP-39 standard. One seed derives keys for many chains at once. So a single broken generator in one app quietly exposes Bitcoin, Ethereum and over a dozen other blockchains.
How attackers actually cashed out
Coinspect confirmed a coordinated sweep on May 27. It pulled roughly $3.1 million out of 431 wallets in one day. A further $2.1 million in USDT was stolen from a single exposed wallet shortly after that. The pattern is simple. Rebuild candidate phrases from the weak generator, derive the addresses they produce, then check the public blockchain for any that still hold funds. No password is guessed and no exchange is breached. The wallet’s own backup does the work for the attacker.
Who is exposed to the Ill Bloom vulnerability
Hardware wallets are not affected. Most current, actively maintained software wallets are not affected either. The risk concentrates in older or lesser-known mobile apps and browser extensions, some still in circulation since 2018. Coinspect has identified five vulnerable implementations internally. It has withheld their names, following a staged disclosure process while it notifies vendors directly.
By June 30, the firm had catalogued 2,114 exposed addresses. They span Bitcoin, Ethereum, Rootstock, Tron and Polygon. Solana, BNB Chain, Monad, Arbitrum, Gnosis, Optimism, Base, Avalanche, Linea and HyperEVM are also flagged as affected chains. Bitcoin carries the largest confirmed loss, about $2.57 million. One address alone lost more than $1.1 million.
How to check and fix your own wallet
- Look up any address you control at illbloom.org, the checking tool Coinspect published alongside its research.
- If an address matches, assume the recovery phrase behind it is fully compromised, not just at risk.
- Do not reuse the phrase and do not simply update the app. The weakness lives in how the phrase was originally generated. Patching the software after the fact does nothing to fix a phrase that already exists.
- Generate a completely new wallet, ideally on a hardware device or a current, well-audited software wallet, and move funds across before anyone else finds the old one.
- If you provision or manage wallets for other people, such as a company treasury or client accounts, check every wallet created since 2018. Do not assume the problem is limited to personal use.
Coinspect notes that vulnerable wallets appear to have kept being generated in recent weeks. That means at least one of the five affected apps had not shipped a fix as of publication. Treat this as an active exposure, not a historical footnote, until a vendor confirms otherwise.
The lesson for anyone auditing wallet software
The wider lesson applies beyond this one bug. Wallet software rarely publishes any evidence of how it generates entropy, and most audits never test for it directly. Anyone auditing wallet code, whether for a client or independent research, should sample generated phrases and check their statistical distribution rather than trust the library it calls. That single test would have caught Ill Bloom years before real funds were at risk.
One more practical point for anyone running a fleet of wallets on behalf of others: age alone is not a reliable signal. A wallet generated in 2018 and a wallet generated last month from the same flawed app carry the same weakness. Coinspect’s checking tool is the only way to know for certain, so run every address you manage through it rather than relying on when the wallet was created.
Coinspect has not said when, or whether, it will name the five affected apps. Vendor notification is still underway, and staged disclosure means details stay limited until fixes are ready. That leaves users to do the legwork themselves for now: check your addresses against the Ill Bloom vulnerability list, retire anything that matches, and do not wait for a press release before you move funds to a wallet you generated fresh.