@polymarkets/clob-client-v2npm
@polymarkets/clob-client-v2 is a confirmed malicious npm package (MAL-2026-14050) that typosquats a legitimate package to trick installs (malicious version 1.0.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @polymarkets/clob-client-v2 (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @polymarkets/clob-client-v2 (version 1.0.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @polymarkets/clob-client-v2 across your stack and pipelines.
If you installed it — respond
@polymarkets/clob-client-v2 is a typosquat — you almost certainly intended a legitimately-named package. Remove @polymarkets/clob-client-v2, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @polymarkets/clob-client-v2 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @polymarkets/clob-client-v2 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @polymarkets/clob-client-v2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.