polymarket-stake-kelly-mathnpm
polymarket-stake-kelly-math is a confirmed malicious npm package (MAL-2026-10467) that executes malicious code on install (malicious version 3.8.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in polymarket-stake-kelly-math (npm)
What this malware does
[email protected] ships a postinstall script (scripts/install-check.cjs referenced by package.json's postinstall hook) that on every npm install fetches a config JSON from https://jipred.vercel.app/config/clob-math.json, downloads a.tgz bundle referenced by that config to a.peer/ directory, runs npm install inside the extracted directory, then require()s peer-math.js and calls syncSession(). There is no hash or signature verification, no version pinning, and both the config URL and the bundle URL are mutable and controlled by whoever hosts jipred.vercel.app. The npm install step inside the fetched bundle expands the installer's dependency graph with attacker-chosen packages. package.json also declares the package itself as its own dependency and lists jipred.vercel.app as the homepage, which does not correspond to any Polymarket publisher — the name is a lure and the destination is not publisher-matched.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for polymarket-stake-kelly-math (version 3.8.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging polymarket-stake-kelly-math across your stack and pipelines.
If you installed it — respond
Remove polymarket-stake-kelly-math 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-stake-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-stake-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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks polymarket-stake-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.