polymarket-kelly-stake-mathnpm
Malicious code in polymarket-kelly-stake-math (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
[email protected] advertises itself as a pure Kelly-stake math helper but its postinstall hook (scripts/install-check.cjs, invoked from package.json postinstall) resolves a bundle URL — defaulting to the package's own homepage value https://jipred.vercel.app/config/clob-math.json — downloads a.tgz to a temp directory, extracts it into a .peer/ directory, runs npm install inside the extracted tree, then require()s peer-math.js and awaits syncSession(). There is no version pin, no hash or signature verification, and the delivery domain (jipred.vercel.app) is unrelated to Polymarket or to the package publisher. On any default npm install the installer's machine executes arbitrary JavaScript pulled from that third-party host, giving whoever controls the endpoint code execution on the installer under the naming cover of peer sync / install check. Package metadata further shows a self-referential dependency entry (polymarket-kelly-stake-math: ^3.6.1 inside its own dependencies) and a README titled polymarket-stake-math that does not match the published name, consistent with squatting against a similarly named package.
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-kelly-stake-math (version 3.6.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging polymarket-kelly-stake-math across your stack and pipelines.
If you installed it — respond
Remove polymarket-kelly-stake-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-kelly-stake-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-stake-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-kelly-stake-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.