polymarket-kelly-stake-math (npm) · Malicious Code
Affects polymarket-kelly-stake-mathSource GCVE Database
Malicious package : remove polymarket-kelly-stake-math and rotate any secrets on hosts that installed it.
Data as of 12 Jul 2026, 09:18 UTC
Malicious package
Published to npm · OSV MAL-2026-10070
What to do
Remove polymarket-kelly-stake-math from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmpolymarket-kelly-stake-math | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (9798cce0effcbcf5ed3295f322a375bb1a3cbb7e9db4b7d88c802bf5116639e3) polymarket-kelly-stake-math@3.6.1 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. ## Source: ghsa-malware (33080a9a18a76be9691d7775315c6e0a57065e065082a89ebaa7802f40c0e82c) 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.