Which versions of polymarket-math-stake-kelly are malicious?

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

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

Remove polymarket-math-stake-kelly from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

If polymarket-math-stake-kelly was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is polymarket-math-stake-kelly part of a known attack campaign?

Yes — polymarket-math-stake-kelly is associated with the IN-MAL-2026-010275 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-math-stake-kelly across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for polymarket-math-stake-kelly (version 3.7.2).

Malicious package

polymarket-math-stake-kellynpm

Advisory published Jul 13, 2026Updated Jul 13, 2026

polymarket-math-stake-kelly is a confirmed malicious npm package (MAL-2026-10466) that executes malicious code on install (malicious version 3.7.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in polymarket-math-stake-kelly (npm)

MAL-2026-10466

Immediate action

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

npm uninstall polymarket-math-stake-kelly

What this malware does

[email protected] runs scripts/install-check.cjs as a postinstall hook. The script reads a config URL (defaulting to https://jipred.vercel.app/config/clob-math.json), downloads a.tgz bundle referenced by that config to a local.peer/ directory, runs npm install inside it, then require()s the extracted peer-math.js and invokes syncSession(). The bundle URL is unpinned, unhashed, and served from an anonymous Vercel deployment unrelated to any documented publisher; the fetched JavaScript executes with the installer's privileges on every npm install. The manifest additionally lists the package itself as a dependency (polymarket-math-stake-kelly: ^3.7.2), which combined with the network-fetching postinstall can cause repeated install-hook re-triggering.

Malicious versions

1 flagged

3.7.2

Indicators of compromise (SHA-256)

408b5fd87b4b328671330e1ddb9333eb5d68d9a873f30237bd886a7632f038b5

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for polymarket-math-stake-kelly (version 3.7.2).
If you installed it — respond
Remove polymarket-math-stake-kelly from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If polymarket-math-stake-kelly was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-010275

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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