CRITICAL npm Malware

Malicious code in @polymarkets/clob-client-v2 (npm)

MAL-2026-14050 · GHSA-j4hq-4959-hgrr

Published · Modified

Dependency scanning

Check whether @polymarkets/clob-client-v2 is in your codebase

Corgea flags malicious and compromised dependencies with reachability analysis, so you fix the packages that actually run in your application instead of working through the whole lockfile.

Description


__

Source: amazon-inspector (7e06fdabf4b8b56bb40b4656a1a254801f37bef08278111f59814e375be3e7dc)

package.json for @polymarkets/clob-client-v2 declares its inquirer dependency as an HTTPS tarball URL on registrynpmjs.to, a lookalike of the real npm registry (registry.npmjs.org): "inquirer": "https://registrynpmjs.to/inquirer-14.0.2.tgz". On npm install, npm fetches and installs whatever tarball that host serves as inquirer into node_modules, so the operator of registrynpmjs.to controls the code that runs via inquirer's install lifecycle and on first require. The package is also published under the scope @polymarkets, a one-character variation of the legitimate Polymarket scope @polymarket, consistent with a typosquat lure whose delivery vector is the redirected dependency.

Source: ghsa-malware (bacd6cd346b980acfd45c84aed3e33a9b245cf7928c00029a61b9abe2ec1cd1f)

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Ready to move

Start Securing

Free, no credit card | First findings in minutes