Executive Summary
In August 2026, Coinspect identified a critical vulnerability in the JavaScript cryptography library CryptoJS, specifically in the WordArray.random() function. This function, introduced 12 years prior, utilized a weak random number generator that compromised the entropy of recovery phrases generated by several cryptocurrency wallet applications. As a result, attackers exploited this weakness to drain approximately $5.7 million from affected wallets across two major incidents since late May 2026. The compromised wallets include RRWallet, Bexo Wallet, NanChat, Bitcoin Libre, and Milo, with varying degrees of remediation and discontinuation.
This incident underscores the critical importance of robust cryptographic practices in software development, especially in applications handling sensitive financial data. The exploitation of weak random number generators highlights the necessity for developers to employ secure entropy sources and for organizations to conduct thorough security audits of third-party libraries to prevent similar vulnerabilities.
Why This Matters Now
The CryptoJS vulnerability highlights the urgent need for developers to ensure the use of secure random number generators in cryptographic applications. As cryptocurrency adoption grows, the security of wallet applications becomes paramount to prevent significant financial losses due to exploitable weaknesses.
Attack Path Analysis
Attackers exploited a weak random number generator in the CryptoJS library to predict wallet recovery phrases, leading to unauthorized access and theft of cryptocurrency funds. The compromised recovery phrases allowed attackers to escalate privileges within the wallet applications. With access to multiple wallets, attackers moved laterally to compromise additional accounts. They established command and control by maintaining persistent access to the compromised wallets. Attackers exfiltrated cryptocurrency funds from the compromised wallets to their own accounts. The impact was significant financial loss for users and reputational damage for the affected wallet providers.
Kill Chain Progression
Initial Compromise
Description
Attackers exploited a weak random number generator in the CryptoJS library to predict wallet recovery phrases, leading to unauthorized access and theft of cryptocurrency funds.
Related CVEs
CVE-2020-36732
CVSS 5.3The crypto-js package before version 3.2.1 for Node.js generates random numbers by concatenating the string '0.' with an integer, making the output more predictable than necessary for cryptographic operations.
Affected Products:
Brix crypto-js – < 3.2.1
Exploit Status:
no public exploitCVE-2023-46233
CVSS 9.1Prior to version 4.2.0, crypto-js PBKDF2 defaults to SHA1 with a single iteration, making it significantly weaker than current industry standards.
Affected Products:
Brix crypto-js – < 4.2.0
Exploit Status:
no public exploit
MITRE ATT&CK® Techniques
Weaken Encryption
Unsecured Credentials: Credentials In Files
Obtain Capabilities: Tool
Supply Chain Compromise: Compromise Software Supply Chain
Valid Accounts
Phishing: Spearphishing Attachment
Application Layer Protocol: Web Protocols
Exfiltration Over C2 Channel
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Secure Cryptographic Key Generation
Control ID: 3.5.1
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA – ICT Risk Management Framework
Control ID: Article 6
CISA ZTMM 2.0 – Data Security
Control ID: 3.1
NIS2 Directive – Security Measures
Control ID: Article 21
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Financial Services
CryptoJS weak RNG vulnerability in wallet applications resulted in $5.7M cryptocurrency theft, exposing financial institutions using affected JavaScript libraries for secure transaction processing.
Computer Software/Engineering
Supply chain vulnerability in CryptoJS library demonstrates critical risks in software development pipelines, affecting applications using compromised random number generation for security-sensitive operations.
Computer/Network Security
Weak entropy generation in cryptocurrency wallets highlights fundamental cryptographic implementation flaws, requiring enhanced security validation and threat detection capabilities across blockchain security platforms.
Internet
Browser extension and mobile wallet vulnerabilities affecting thousands of users across EVM-compatible networks demonstrate widespread exposure of internet-based cryptocurrency services to entropy attacks.
Sources
- CryptoJS Weak RNG Behind $5.7 Million in Drains Affects Five Crypto Wallet Appshttps://thehackernews.com/2026/08/cryptojs-weak-rng-behind-57-million-in.htmlVerified
- CryptoJS.lib.WordArray.random() uses a weak PRNG (Ill Bloom)https://github.com/brix/crypto-js/security/advisories/GHSA-rg76-677x-56q9Verified
- Identifying the Wallets Behind Vulnerable Recovery Phraseshttps://illbloom.org/articles/identifying-wallets-vulnerable-recovery-phrases/Verified
- Crypto-js Information Disclosure Flawhttps://www.sentinelone.com/vulnerability-database/cve-2020-36732/Verified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Aviatrix Zero Trust CNSF is pertinent to this incident as it could have limited the attacker's ability to move laterally and exfiltrate data by enforcing strict segmentation and controlled egress policies.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: While Aviatrix CNSF may not prevent the initial compromise due to application-level vulnerabilities, it could limit the attacker's ability to exploit compromised credentials across the network.
Control: Zero Trust Segmentation
Mitigation: Aviatrix Zero Trust Segmentation could limit the attacker's ability to escalate privileges by enforcing least-privilege access controls, thereby reducing the scope of accessible resources.
Control: East-West Traffic Security
Mitigation: Aviatrix East-West Traffic Security could constrain lateral movement by monitoring and controlling internal traffic, thereby reducing the attacker's ability to access additional accounts.
Control: Multicloud Visibility & Control
Mitigation: Aviatrix Multicloud Visibility & Control could reduce the attacker's ability to maintain persistent access by providing comprehensive monitoring and control over multicloud environments.
Control: Egress Security & Policy Enforcement
Mitigation: Aviatrix Egress Security & Policy Enforcement could limit data exfiltration by controlling outbound traffic and enforcing strict egress policies.
While Aviatrix CNSF may not eliminate all impacts, it could reduce the overall blast radius by containing the attacker's reach and limiting the extent of compromised resources.
Impact at a Glance
Affected Business Functions
- Cryptocurrency Wallet Management
- User Account Security
Estimated downtime: N/A
Estimated loss: $5,700,000
Compromised recovery phrases leading to unauthorized access to cryptocurrency wallets.
Recommended Actions
Key Takeaways & Next Steps
- • Implement secure random number generators in cryptographic operations to prevent predictable outputs.
- • Regularly audit and update third-party libraries to mitigate known vulnerabilities.
- • Enforce least privilege access controls to limit the impact of compromised credentials.
- • Monitor for anomalous access patterns to detect unauthorized activities.
- • Educate users on the importance of secure recovery phrase management and prompt them to regenerate phrases if vulnerabilities are discovered.
