Which versions of clob-math-v2 are malicious?

The following npm versions of clob-math-v2 are flagged malicious: 2.0.1. Treat any of these as compromised.

How do I remediate clob-math-v2 if I installed it?

clob-math-v2 is a typosquat — you almost certainly intended a legitimately-named package. Remove clob-math-v2, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed clob-math-v2 — how do I know if it already compromised me?

If clob-math-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.

Is clob-math-v2 part of a known attack campaign?

Yes — clob-math-v2 is associated with the IN-MAL-2026-009361 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find clob-math-v2 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for clob-math-v2 (version 2.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging clob-math-v2 across your stack and pipelines.

Malicious package

clob-math-v2npm

Malicious code in clob-math-v2 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10083

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall clob-math-v2

What this malware does

Package presents itself as a Polymarket CLOB math SDK but is published from a domain not owned by Polymarket (polymarket-clob-service.vercel.app; the real project is polymarket.com). The postinstall script reads a config JSON from that lookalike host (path /config/clob-math.json), extracts a peerBundle tarball URL from the response, downloads the.tgz, extracts it, runs npm install inside the extracted tree, then require()s peer-math.js from it and invokes syncSession(). The fetched code is unpinned, unverified, served from a mutable attacker-controlled endpoint, and executes automatically on every npm install. Combined with the Polymarket brand impersonation in the package name and homepage, this is a typosquat-lured install-time dropper that gives the publisher arbitrary code execution on the installer's machine.

Malicious versions

1 flagged

2.0.1

Indicators of compromise (SHA-256)

4cd6b75c25c58b35cca1a29500c1608eb1b121e37bd9305ff549d05d73b69031

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for clob-math-v2 (version 2.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging clob-math-v2 across your stack and pipelines.
If you installed it — respond
clob-math-v2 is a typosquat — you almost certainly intended a legitimately-named package. Remove clob-math-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 clob-math-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 clob-math-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

No. clob-math-v2 on npm has been identified as a malicious package (version 2.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009361

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks clob-math-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.

Malware detection Runtime egress monitoring