<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Weak-Rng on CuraSec</title><link>https://curasec.metacog.co.kr/tags/weak-rng/</link><description>Recent content in Weak-Rng on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 06 Aug 2026 13:03:19 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/weak-rng/index.xml" rel="self" type="application/rss+xml"/><item><title>CryptoJS Weak RNG Linked to $5.7M Crypto Wallet Drains</title><link>https://curasec.metacog.co.kr/insights/2026-08-06-cryptojs-weak-rng-behind-5-7-million-in-drains-affects-five/</link><pubDate>Thu, 06 Aug 2026 13:03:19 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-06-cryptojs-weak-rng-behind-5-7-million-in-drains-affects-five/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> Audit any use of CryptoJS.lib.WordArray.random() in your codebase — it provides insufficient entropy for cryptographic key generation; replace with Web Crypto API&amp;rsquo;s crypto.getRandomValues() immediately and review whether any generated secrets need rotation.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> Active drains are targeting end-user crypto wallets rather than enterprise estates; no enterprise-relevant IOCs or ATT&amp;amp;CK-mappable TTPs are present, but the weak-RNG exploitation pattern is worth tracking for future detection design.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>