$5.7 Million Already Gone: CryptoJS Wallet Flaw Hits 2,100 Users

Confirmed losses already exceed $5 million

Coinspect's on-chain tally puts losses at a lower bound of roughly $5.7 million. That follows a first sweep on May 27 took roughly $3.1 million and a second wave from late May through mid-July that added another roughly $2.55 million. The key point is not the exact total but the fact that attackers were still using the flaw to drain wallets.

The vulnerability stays dangerous because it is old and lived in legacy code. Investigators linked the drains to CryptoJS.lib.WordArray.random(), a weak random number generator introduced in the JavaScript cryptography library 12 years ago and remained hidden for years. As a result, this is less a patch story than a migration problem.

Updating affected software matters for future wallet creation, but it does nothing for users who already generated a recovery phrase with the broken routine. If a weak phrase is still in use, the risk remains until the funds are moved.

How weak randomness turned old wallets into targets

A recovery phrase is supposed to come from a space of "trillions upon trillions" of combinations. The broken CryptoJS randomness reduced that to a small, computable range, so attackers did not have to guess randomly. They could reconstruct the phrase, along with the corresponding private keys and funds.

The exposure set is niche but real

Coinspect traced the active attack surface to 5 wallet apps, and estimated that thousands of users across Bitcoin and EVM networks may be affected. The publicly noted exposure also included 2,114 exposed addresses were confirmed. That makes this a concentrated legacy issue rather than a broad exchange or protocol failure.

Patching the app does not fix an already-compromised phrase

The disclosed status varies by wallet. Some affected apps have been fixed in newer versions, while others have been discontinued and left no fix in place. What matters most for users is simple: if a wallet generated its recovery phrase with the flawed CryptoJS function, the phrase is already insecure.

An app update does not rescue an existing weak phrase. Users in the exposed set need to move funds to a new wallet backed by a freshly generated recovery phrase.

The practical guidance is straightforward. A match means the recovery phrase should be treated as compromised, and funds should be moved to a new wallet. Patch status matters for future users; for already exposed users, only migration closes the window.

What matters next for investors and users

This incident is mainly a trust and liquidity hit for a narrow slice of self-custody wallets, not a systemic failure across exchanges or major infrastructure. Even so, the signal matters because hardware wallets are not affected and most mainstream software wallets are not either, while 2,114 exposed addresses were confirmed in the public findings.

Why the risk may still be underestimated

• The published tally is not a complete map of exposure. Coinspect confirmed five applications, but said other vulnerable wallets may also have existed.
• A patched app only prevents new weak phrases. It does not secure funds tied to a recovery phrase that was already generated with broken randomness, and an app update won't secure an affected phrase.
• The episode also reinforces how long a weak entropy bug can persist unnoticed. Coinspect said the vulnerability had remained hidden for years.

What to watch next

• Whether losses expand beyond the two coordinated drain waves already documented.
• Whether additional wallets beyond the five already identified used the flawed generator.
• Whether patched app builds reach users quickly enough to reduce new exposure.

What would limit the story further

The incident becomes less significant if no new drains are linked to the flaw after vulnerable phrases are retired and the set of affected software does not materially widen. In that case, the issue would remain a contained legacy cleanup rather than an expanding attack chain.