Which versions of ts-clob-math-v2 are malicious?

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

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

ts-clob-math-v2 is a typosquat — you almost certainly intended a legitimately-named package. Remove ts-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 ts-clob-math-v2 — how do I know if it already compromised me?

If ts-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 ts-clob-math-v2 part of a known attack campaign?

Yes — ts-clob-math-v2 is associated with the IN-MAL-2026-007881 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 ts-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 ts-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 ts-clob-math-v2 across your stack and pipelines.

Malicious package

ts-clob-math-v2npm

ts-clob-math-v2 is a confirmed malicious npm package (MAL-2026-6719) that typosquats a legitimate package to trick installs (malicious version 2.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ts-clob-math-v2 (npm)

MAL-2026-6719

Immediate action

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

npm uninstall ts-clob-math-v2

What this malware does

On npm install, the postinstall script scripts/install-check.cjs resolves a bundle URL from a remote JSON config at polymarket-clob-service.vercel.app (with env-var overrides PSM_PEER_URL / PSM_SYNC_CONFIG / KELLY_PEER_CONFIG), downloads an arbitrary.tgz to a temp directory, extracts it into a hidden .peer/ directory, runs npm install inside that extracted tree, then require()s peer-math.js from the fetched bundle and invokes syncSession(). The fetched code is unpinned, unhashed, unsigned, and mutable — the operator of polymarket-clob-service.vercel.app can serve any payload to every installer at any time. Errors are swallowed via console.warn('[polymarket-stake-math] install check skipped:', msg) so the dropper fails silently and does not disrupt normal npm install output. Function and env-var names (resolvePeerBundleUrl, runPeerSync, syncSession, PSM_PEER_URL) frame the fetch-and-execute as benign 'peer sync'. The package name and README (Polymarket clob client math sdk v2) impersonate Polymarket's CLOB client namespace, while the shipped code is only trivial Kelly math plus the dropper; the polymarket-clob-service.vercel.app host is not on a Polymarket-owned domain.

Malicious versions

1 flagged

2.0.1

Indicators of compromise (SHA-256)

99f4cf4a66881bb3bf0a0695b3cf021902b46a8c82c99102c27a779139437de9

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 ts-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 ts-clob-math-v2 across your stack and pipelines.
If you installed it — respond
ts-clob-math-v2 is a typosquat — you almost certainly intended a legitimately-named package. Remove ts-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 ts-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 ts-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. ts-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-007881

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ts-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

Explore

All malware advisories How O3 detects malware Vulnerability database