Loading story…
Trail of Bits reported additional cryptographic bugs in the widely used JavaScript package elliptic after testing it with Google's Wycheproof suite, adding to earlier public disclosures that had already produced multiple CVEs. The findings renewed concerns that the library, which is broadly embedded across the Node.js ecosystem for elliptic-curve cryptography, may produce insecure behavior under malformed or edge-case inputs and has accumulated unresolved security issues.
A follow-on report urged developers to remove elliptic from production dependencies altogether, citing the newly highlighted flaws, previously disclosed vulnerabilities, and alleged timing side-channel weaknesses in scalar-multiplication code paths. As a migration path, the author released elliptic-to-noble, a compatibility shim intended to preserve the elliptic API while swapping in noble-curves, and called for urgent ecosystem-wide replacement of the package rather than continued reliance on an apparently unmaintained cryptographic library.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
Trail of Bits published a blog post reporting cryptographic bugs in the JavaScript npm package elliptic discovered using Wycheproof. The disclosure was accompanied by two CVEs affecting elliptic.
In an addendum, the author said they reviewed elliptic source code beyond the Trail of Bits issues and publicly disclosed additional alleged timing side-channel weaknesses. The claims specifically cited fixedNafMul, _wnafMul, and _wnafMulAdd code paths as leaking information through branch-dependent behavior.
The author published elliptic-to-noble, a shim package that preserves the elliptic API while replacing its implementation with noble-curves. It was presented as a practical mitigation to help projects reduce risk and migrate away from elliptic.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Security researchers reported an npm supply-chain compromise involving a malicious package, `polymarket-clob`, that targeted cryptocurrency users by exfiltrating sensitive local files (including `.env`, `wallets.json`, and `keys/*.json`) to attacker-controlled infrastructure. The package was published in the npm registry, downloaded at least 189 times (lower bound), and later removed and replaced with a security placeholder; analysis of the code and infrastructure pivoting linked the campaign to broader activity consistent with wallet-drainer operations and **Vidar** stealer-related infrastructure, including reuse of SSH fingerprints and consistent hosting patterns. Separately, researchers disclosed **six JavaScript “zero-day” bypass issues** across multiple package managers—**npm, pnpm, vlt, and Bun**—that undermine common defensive controls used to reduce supply-chain risk, including disabling lifecycle scripts and relying on lockfile integrity. The issues (dubbed **“PackageGate”**) reportedly enable paths to regain install-time code execution or weaken integrity guarantees via mechanisms such as Git dependency handling, tar extraction behaviors, and incomplete integrity coverage for URL-based tarballs; pnpm, vlt, and Bun were reported as patched, while npm characterized the behavior as “works as expected,” raising concern that package-manager-level weaknesses could enable large-scale compromise even in hardened environments.
Jun 29, 2026
A wave of disclosures has exposed multiple critical flaws in the Node.js sandbox library **vm2**, showing that untrusted JavaScript can break out of the sandbox and execute commands on the host. GitHub advisories describe several distinct escape paths affecting versions as old as `3.9.6` and, in some cases, up to `3.11.3`, including a breakout through Node.js `inspect`, a Promise species bypass that defeats an earlier patch, prototype pollution through vm2’s bridge to host intrinsic prototypes, and a `NodeVM` misconfiguration path where `nesting: true` lets code bypass `require: false` and load `vm2` recursively to reach modules such as `child_process`. Public proof-of-concepts show attackers recovering the host `process` object and invoking host commands, turning vm2 from a containment boundary into a route to full host compromise. Additional reporting and upstream changes indicate the problems are broader than a single bug. Semgrep documented a new sandbox escape, while vm2 maintainers added regression tests covering descriptor- and prototype-traversal techniques used to recover host constructors such as `Function`, `AsyncFunction`, and `GeneratorFunction`, as well as callback sanitization bypasses tied to Promise handling. A later roundup described five critical vulnerabilities with no practical configuration-based workaround for deployments that execute untrusted code, and urged upgrades to **vm2 `3.11.4` or later**. The advisory backlog on the project’s GitHub page shows a concentrated set of newly published sandbox escape, builtin bypass, and host code execution issues, underscoring that organizations relying on vm2 for isolation should treat affected environments as potentially compromised.
Jun 29, 2026
A critical vulnerability tracked as **`CVE-2026-71851`** was disclosed in the JavaScript cryptography library **`crypto-js`**, affecting versions prior to **`4.0.0`**. The flaw lies in **`CryptoJS.lib.WordArray.random()`**, which used a custom Multiply-With-Carry pseudorandom number generator seeded with **`Math.random()`** rather than a cryptographically secure operating-system entropy source. That design sharply reduced the effective entropy of supposedly strong random outputs, making generated keys, initialization vectors, and other secrets potentially predictable or reconstructable. The weakness is especially serious for cryptocurrency wallets and decentralized applications that used the function to generate entropy for **BIP39 recovery phrases**, because attackers may be able to recover private keys and steal funds from affected wallets. Reports assign the issue a **CVSS v3.1 score of 9.0** and map it to **`CWE-331`**, **`CWE-338`**, and **`CWE-334`**. The issue is fixed in **`crypto-js 4.0.0`**, and secure alternatives cited for randomness generation include browser **`window.crypto.getRandomValues()`** and Node.js **`crypto.randomBytes()`**.
Aug 8, 2026