Cybersecurity firm **Coinspect** has unveiled a significant flaw impacting certain cryptocurrency wallets, dubbed **Ill Bloom**, which is actively being exploited by attackers. The vulnerability lies in how some wallet software generates its recovery phrases, also known as seed phrases. When these phrases are created with weak cryptographic randomness, attackers can deduce them and gain full control over the associated funds. **Coinspect** has confirmed a coordinated attack on May 27 that siphoned approximately $3.1 million from 431 wallets. This was followed by an additional $2.1 million in **USDT** stolen from a separately exposed wallet, pushing confirmed losses beyond $5 million. As **Coinspect** states, "if funds recently moved without your permission, this vulnerability may be why." ### Who is Affected? While the majority of users are likely unaffected, particularly those using hardware wallets or mainstream software wallets, the primary risk lies with older or less common mobile applications and browser extensions, some dating back to 2018. **Coinspect** has not publicly named the specific vulnerable applications. To determine if your wallet is at risk, users can paste their public wallet address into the free checker available at [illbloom.org](https://illbloom.org). A match indicates that the recovery phrase should be considered compromised, and funds should be immediately transferred to a new, secure wallet. ### The Technical Breakdown Every self-custody wallet relies on a recovery phrase, typically 12 or 24 words, chosen from an astronomically vast pool to ensure unpredictability. The affected wallets, however, utilized a weak random-number generator during phrase creation. This significantly reduced the pool of possible phrases to a range that attackers could systematically search. **Coinspect** meticulously reconstructed the attack, enumerating the full set of phrases the weak generator could produce, deriving the corresponding wallet addresses, and then cross-referencing these with public blockchain records for addresses still holding funds. This process generated a watchlist of inherently weak wallets, irrespective of the application that created them. ### The Scope of the Theft As of June 30, **Coinspect** had identified 2,114 exposed addresses with on-chain activity across **Bitcoin**, **Ethereum**, **Rootstock**, **Tron**, and **Polygon**. The May 27 sweep disproportionately affected **Bitcoin** wallets, accounting for roughly $2.57 million, with one single **Bitcoin** address losing over $1.1 million. The coordinated nature of the theft was evident as hundreds of unrelated wallets transferred their balances to the same few collection addresses within a matter of hours. The subsequent $2.1 million theft underscores the persistent risk. **Coinspect** observed an exposed wallet on June 10 with **USDT** funds still at risk, despite the owner's seed having been compromised earlier. Attempts to warn the owner through associated exchanges were unsuccessful, and the funds were subsequently stolen. The researchers noted that while they could derive the exposed keys, they could not move the funds to safety, as "once a seed phrase is compromised, possessing the key no longer proves legitimate ownership." These reported losses are considered a minimum, not a maximum. The set of exposed wallets continues to grow as **Coinspect** discovers more vulnerable seed generation paths. At its peak in 2022, the same set of vulnerable wallets held an estimated $12.56 million in value, though much of this had depreciated with the market before the recent attacks. ### Immediate Action Required Users should check every public wallet address tied to the same seed phrase using [illbloom.org](https://illbloom.org). The checker supports **Bitcoin**, **Tron**, **Solana**, and **Ethereum-style** addresses (including **Ethereum**, **Polygon**, **BNB**, and other **EVM** chains). If your address matches: 1. **Treat the recovery phrase as compromised.** Even if funds haven't moved yet, they are not safe. 2. **Create a brand-new wallet** with a completely new recovery phrase. Ensure the application generates a fresh set of 12 to 24 words, rather than asking you to input an old phrase. 3. **Move all funds to the new, secure wallet.** Reinstalling the old app or importing the compromised phrase elsewhere will not secure your assets. Even wallets that were spared in the initial attacks are not safe if their addresses match the compromised list. **Coinspect** noted that the May 27 attackers often skipped accounts holding less than $5, but these seeds remain compromised, making any future deposits vulnerable. If your address matches, discontinue use of that wallet immediately. **Beware of Scams:** During such incidents, scammers often emerge offering to "rescue" funds. A legitimate checker will never ask for seed phrases, private keys, signatures, or to send funds for recovery. Never input your recovery phrase, private key, password, or backup file into any suspicious site or message. For maximum security, transfer funds to a hardware wallet, ensuring a *fresh* phrase is generated on the device. ### A Recurring Problem The **Ill Bloom** vulnerability is not a new phenomenon but rather a recurring failure in the cryptocurrency space. It echoes previous incidents like **Milk Sad** (**CVE-2023-39910**) in 2023, which impacted the **Libbitcoin Explorer** command-line tool and led to millions in losses. Similarly, **CVE-2023-31290** affected the **Trust Wallet browser extension** in the same year, allowing for compromise in under a day. Another example is **Randstorm**, a weak-randomness flaw covered by **The Hacker News** in 2023, which left **Bitcoin** wallets created between 2011 and 2015 vulnerable due to poor random number generation in their underlying browser code. The resolution for all these vulnerabilities is consistently the same: move funds to a new wallet generated with robust cryptographic practices. ### What's Next? This cycle of predictable random-number generators compromising wallets re-emphasizes the need for stringent cryptographic standards in wallet development. **Coinspect** has identified five vulnerable wallet implementations and is actively researching others. While they are not publicly naming these implementations at this stage, their investigation involves tracing on-chain funding links, searching **GitHub** for matching code, and reverse-engineering closed-source Android apps and Chrome extensions to understand their recovery phrase generation methods. This ongoing discovery process suggests that more vulnerable implementations may yet be found, highlighting the persistent threat posed by fundamental cryptographic weaknesses. *Updated July 10, 2026 with **Coinspect**'s responses to The Hacker News.*