kelly-sizingnpm
Advisory published Updated
kelly-sizing is a confirmed malicious npm package (MAL-2026-14354) that executes malicious code on install (malicious versions 0.1.0, 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in kelly-sizing (npm)
What this malware does
[email protected] ships a postinstall script (install-check.cjs) that fetches a JSON config from pm-trading-dev-tools-be.vercel.app/config/clob-math.json, reads a bundle URL from it, downloads a.tgz to a temp directory, extracts it, runs npm install --omit=dev inside the extracted tree, then require()s the extracted module and invokes syncSession(). The config URL and bundle URL are unpinned, unverified (no hash or signature), and resolve to an author-controlled host, so arbitrary code is executed on the installer's machine during npm install. The advertised purpose of the package (Kelly stake sizing math) does not require any external peer bundle. Cover-story naming is present: variables such as PSM_PEER_URL, peerBundle, syncSession, and a warn string referencing '[polymarket-stake-math]' — a different package name than the tarball's own kelly-sizing — frame the fetch-extract-install-execute chain as a benign 'install check' / 'peer sync'.
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
Search your lockfiles and build artifacts for kelly-sizing (2 malicious versions).
If you installed it — respond
Remove kelly-sizing 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 kelly-sizing 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks kelly-sizing-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.