MalwarePublished 1 Jul 2026Updated 5 Aug 2026

polymarket-risk-manager (npm) · Malicious Code

Affects polymarket-risk-managerSource GCVE Database

Malicious package : remove polymarket-risk-manager and rotate any secrets on hosts that installed it.

Data as of 26 Oct 2026, 16:12 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-6712

What to do

Remove polymarket-risk-manager 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-risk-manager	Affected 3.1.0 – 3.5.2 4 affected builds	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 (54bfddce038bb64117d6850bb2977f8cee17704212e12e6214fb495b9d4cee79) On `npm install`, the package's postinstall script reads a config URL from package.json's `homepage` field (https://parket-server-help.vercel.app/config/psm-peer.json), downloads a tarball from the returned bundle URL, extracts it, runs `npm install` inside the extracted directory, and then `require()`s `peer-math.js` from the fetched bundle and invokes `syncSession()` from it. There is no version pin, hash check, or signature verification, and the destination domain (parket-server-help.vercel.app) is not Polymarket-owned despite the polymarket-prefixed package name and brand-adjacent host. The stated purpose of the package — Kelly stake math in a ~40-line kelly.js — does not require any network bundle. The postinstall code is framed as a 'peer sync'/'install check', accepts environment overrides (PSM_PEER_URL, PSM_SYNC_CONFIG, KELLY_PEER_CONFIG), and swallows errors as 'install check skipped' to suppress visibility. This is the canonical install-time dropper shape: arbitrary attacker-controlled JavaScript executes inside the installer's Node process during dependency installation. ## Source: ghsa-malware (8d8f215c500de42921e7d9022bedb04a160d16bf595ab338a2bd6b79a384151b) 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.

Impact

Any system that installs or runs polymarket-risk-manager version 3.5.2 is at risk of full compromise due to arbitrary code execution during installation. Attackers may gain complete control over the affected system, potentially accessing all stored secrets and keys. Removal of the package does not guarantee elimination of all malicious artifacts, as the attacker may have already established persistence or installed additional malware.

Defensive guidance

Users should immediately remove polymarket-risk-manager version 3.5.2 from their systems. All secrets and keys on affected systems should be considered compromised and rotated from a separate, trusted environment. Monitor for any signs of compromise and consider rebuilding affected systems to ensure removal of any persistent threats.

Summary

The polymarket-risk-manager npm package (version 3.5.2) includes a postinstall script that reads a configuration URL from the package.json homepage field, downloads a tarball from an attacker-controlled domain (parket-server-help.vercel.app), extracts it, runs npm install inside the extracted directory, and executes a function from the downloaded code. There is no version pinning, hash verification, or signature validation of the downloaded content. The postinstall script suppresses errors to avoid detection. This behavior constitutes a canonical install-time dropper allowing arbitrary attacker-controlled JavaScript execution within the Node.js process during dependency installation. The package's legitimate functionality does not require network access, confirming the malicious intent of the postinstall script.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Jul 2026, 05:47 UTC

Technical details

References

Community reviews