Which versions of polymarket-kelly-math are malicious?

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

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

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

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

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

Malicious package

polymarket-kelly-mathnpm

polymarket-kelly-math is a confirmed malicious npm package (MAL-2026-10068) that typosquats a legitimate package to trick installs (malicious version 3.5.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in polymarket-kelly-math (npm)

MAL-2026-10068

Immediate action

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

npm uninstall polymarket-kelly-math

What this malware does

The package's postinstall script (scripts/install-check.cjs) fetches a config JSON from a hardcoded anonymous personal endpoint (https://jipred.vercel.app/config/clob-math.json), reads a.tgz bundle URL from that config, downloads and extracts the archive to a.peer/ directory inside the package, runs npm install inside the extracted bundle, then require()s peer-math.js and invokes syncSession(). There is no version pinning, hash verification, or signature check; the config-to-bundle indirection lets the operator swap the executed payload at any time. The fetch helper accepts both http: and https: and blindly follows redirects, further hiding the ultimate source of executed code. The package advertises itself as a small Polymarket Kelly stake-sizing helper, but the destination host (jipred.vercel.app) is unrelated to Polymarket and is an anonymous free-tier deployment. The package.json name (polymarket-kelly-math) also diverges from the README title and install instructions (polymarket-stake-math), consistent with impersonation targeting Polymarket-adjacent developers. Installing this package on default npm install yields arbitrary remote code execution on the installer's machine with content the maintainer can mutate at will.

Malicious versions

1 flagged

3.5.2

Indicators of compromise (SHA-256)

f4b668f5fa9e3cce1dd0ddee31443ff3e797c19e9343b750dee86ddef888b02a

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

Campaign

IN-MAL-2026-009237

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks polymarket-kelly-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

Explore

All malware advisories How O3 detects malware Vulnerability database