A long-standing vulnerability in a core JavaScript cryptography library has been identified as the direct cause of a theft campaign resulting in over $5.7 million in stolen digital assets. Researchers from Coinspect confirmed the weakness is located in the function CryptoJS.lib.WordArray.random(), which provided insufficient randomness for the recovery phrase generation process used by at least five separate cryptocurrency wallet applications.
The issue is not a newly discovered flaw but a fundamental deficiency in entropy collection that has persisted for years. Instead of correctly drawing random data from the operating system's secure generator, the function used a predictable, internal method. Attackers from the "Ill Bloom" campaign exploited this weakness, reverse-engineering the pattern to reconstruct private keys and drain funds in two coordinated sweeps since late May. Coinspect’s on-chain analysis quantifies the confirmed losses at a minimum of $5.7 million, with the full extent of compromised addresses still under investigation.
This case exemplifies the risk of "dependency rot"—the silent persistence of flawed legacy components within widely used open-source software. The vulnerable function remained active in production environments across multiple projects, highlighting a governance gap where periodic security reviews failed to catch a critical, long-present defect. For the industry, it underscores that continuous monitoring and verification of security-critical dependencies must become a standard engineering practice, moving beyond one-time integration audits.
The incident is prompting broader reflection on software supply chain integrity in an era of automated development. As AI-assisted coding tools and dependency managers increase efficiency, they can also propagate latent vulnerabilities with reduced human oversight. This necessitates mandatory governance practices for cryptographic libraries, including rigorous provenance and entropy validation. Technology teams worldwide now face the challenge of aligning automated pipelines with these heightened security and compliance standards.
In response, developers must immediately audit their projects for usage of the compromised function and replace it with cryptographically secure alternatives like window.crypto.getRandomValues() for browsers or Node.js's crypto.randomBytes(). Users of affected wallets face an urgent need to migrate assets, as exposed seed phrases cannot be secured. The investigation is also examining potential exposure in non-cryptocurrency applications that may rely on the same flawed entropy source, which will determine remediation timelines across the broader software ecosystem.
While attribution for the Ill Bloom campaign continues, the technical conclusion is clear: reliable cryptographic entropy is a non-negotiable foundation for digital security. This event will likely accelerate industry-wide mandates for transparent entropy sourcing and stricter, continuous dependency governance, fundamentally reshaping development and operational practices for cryptographic security.
一個核心 JavaScript 加密函式庫中長期存在的漏洞，已被確認為導致價值超過 570 萬美元數字資產被盜的竊取行動的直接原因。Coinspect 的研究人員證實，該弱點位於 CryptoJS.lib.WordArray.random() 函數中，該函數為至少五個獨立加密貨幣錢包應用程式所使用的助記詞生成過程提供了不足的隨機性。
問題並非新發現的缺陷，而是熵源收集方面一個持續多年的基本不足。該函數並未正確從作業系統的安全生成器中獲取隨機數據，而是採用了一種可預測的內部方法。「Ill Bloom」行動的攻擊者利用了此弱點，逆向工程該模式以重建私鑰，並自五月底以來進行了兩次協調的資金掃蕩。Coinspect 的鏈上分析將已確認損失量化為至少 570 萬美元，受影響地址的完整範圍仍在調查中。
此案例體現了「依賴腐化」的風險——即有缺陷的遺留元件在廣泛使用的開源軟件中持續默默地存在。這個脆弱的函數在多個項目的生產環境中保持活躍，突顯了一個治理缺口：定期安全審查未能發現一個關鍵且長期存在的缺陷。對業界而言，這強調了持續監控和驗證安全關鍵依賴項必須成為標準的工程實踐，超越單次整合審計的範疇。
此事件促使業界更廣泛地反思在自動化開發時代下的軟件供應鏈完整性。隨著 AI 輔助的編碼工具和依賴管理器提高了效率，它們也可能在較少的人工監督下傳播潛在漏洞。這需要針對加密函式庫實行強制性的治理實踐，包括嚴格的來源和熵驗證。全球的技術團隊現在面臨著將自動化管線與這些更高的安全與合規標準對齊的挑戰。
作為回應，開發者必須立即審計其項目中是否使用了受損的函數，並用加密學安全的替代方案取代它，例如瀏覽器使用的 window.crypto.getRandomValues() 或 Node.js 的 crypto.randomBytes()。受影響錢包的用戶面臨著緊急遷移資產的需求，因為暴露的助記詞無法被保障安全。調查同時也在檢查依賴相同有缺陷熵源的非加密貨幣應用程式可能存在的暴露情況，這將決定更廣泛軟件生態系統的補救時間表。
儘管對 Ill Bloom 行動的歸因仍在進行，但技術結論是明確的：可靠的加密熵是數字安全不可協商的基礎。此事件將可能加速全行業要求透明熵源和更嚴格、持續的依賴項治理的強制令，從根本上重塑加密安全開發與運營實踐。