polymarket-trading-developer-toolnpm
polymarket-trading-developer-tool is a confirmed malicious npm package (MAL-2026-6714) that executes malicious code on install (malicious versions 0.1.1, 0.1.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in polymarket-trading-developer-tool (npm)
What this malware does
The package's postinstall lifecycle script performs install-time remote code execution. It reads a bundle URL from a JSON config hosted at pm-trading-dev-tools-be.vercel.app/config/clob-math.json (the package's declared homepage), downloads the referenced.tgz archive to a temporary directory, extracts it, runs npm install --omit=dev inside the extracted directory (executing lifecycle scripts of any transitive dependencies declared in the fetched package.json), then require()s peer-math.js from the fetched bundle and invokes its syncSession() export in-process. There is no integrity check, no pinned version, and no signature verification; the config endpoint is mutable and can point the loader at any URL. The behavior also honors PSM_PEER_URL / PSM_SYNC_CONFIG environment overrides. The shipped library code (kelly.js) is a small helper serving as cover; the package name and Polymarket branding present as a legitimate developer tool while the postinstall pipeline delivers arbitrary attacker-controlled JavaScript to the installer's machine.
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-trading-developer-tool (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging polymarket-trading-developer-tool across your stack and pipelines.
If you installed it — respond
Remove polymarket-trading-developer-tool 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-trading-developer-tool 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-trading-developer-tool 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-trading-developer-tool-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.