@polymarkets/clob-client-v2 (npm) · Malicious Code
Affects @polymarkets/clob-client-v2Source GCVE Database
Malicious package : remove @polymarkets/clob-client-v2 and rotate any secrets on hosts that installed it.
Data as of 9 Nov 2026, 15:19 UTC
Malicious package
Published to npm · OSV MAL-2026-14050
What to do
Remove @polymarkets/clob-client-v2 from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@polymarkets/clob-client-v2 | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## 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.