Which versions of polymarket-clob-math are malicious?

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

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

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

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

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

Yes — polymarket-clob-math is associated with the IN-MAL-2026-007701 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 polymarket-clob-math 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 polymarket-clob-math (version 1.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging polymarket-clob-math across your stack and pipelines.

Malicious package

polymarket-clob-mathnpm

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

MAL-2026-6556

Immediate action

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

npm uninstall polymarket-clob-math

What this malware does

[email protected] ships a postinstall lifecycle script that performs an install-time remote-code-execution drop. On npm install, the script fetches a JSON config from https://datasecure-service.vercel.app/config/clob-math.json (a non-publisher Vercel host repurposed as the package's homepage), resolves a tarball URL from that config, downloads and extracts the tarball, runs npm install inside the extracted directory, then require()s a file from the bundle and invokes it (syncSession()). The fetched bytes are unpinned, unhashed, mutable, and served from a domain unrelated to any Polymarket or publisher infrastructure. Internal naming (PSM_PEER_URL, runPeerSync, peer-math.js, syncSession, the warning [polymarket-stake-math] install check skipped) frames the loader as a benign peer-dependency sync, and the package name plus README branding (polymarket-stake-math, Kelly-stake-sizing for Polymarket binary markets) impersonate the Polymarket CLOB ecosystem to attract installs. Installing this package executes arbitrary attacker-controlled JavaScript on the installer's machine.

Malicious versions

1 flagged

1.0.4

Indicators of compromise (SHA-256)

d67023e54ba355e9c82fd2a05d2d2448657a3ea9415ff18d3c4669a9fc0afb42

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 polymarket-clob-math (version 1.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging polymarket-clob-math across your stack and pipelines.
If you installed it — respond
polymarket-clob-math is a typosquat — you almost certainly intended a legitimately-named package. Remove polymarket-clob-math, 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 polymarket-clob-math 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 polymarket-clob-math 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. polymarket-clob-math on npm has been identified as a malicious package (version 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007701

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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