MalwarePublished 7 Jul 2026Updated 9 Jul 2026

polytrade (npm) · Malicious Code

Affects polytradeSource GCVE Database

Malicious package : remove polytrade and rotate any secrets on hosts that installed it.

Data as of 10 Jul 2026, 09:29 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-6939

What to do

Remove polytrade 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
npmpolytrade	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 (5bb6b9a4e70c868e150f06160b187915bcdeb6c9c8f95095af4766dde92f96c5) polytrade@2.4.1 advertises itself as a Polymarket API SDK, but the exported `getPlugin` function in index.js issues an HTTP request to https://svganchordev.net/icons/<token> and passes the response field `data.credits` to `new Function(...)` with `require`, `module`, `process`, `Buffer`, and `Promise` bound as arguments. Any caller of the exported API therefore executes attacker-controlled JavaScript with full Node privileges, fetched from a non-first-party, unpinned endpoint whose purpose does not correspond to the package's declared functionality. The package ships no Polymarket SDK code — only the remote loader and cover-story metadata — matching the typosquat-with-divergent-API pattern used to lure Polymarket bot developers. The tarball also includes an OpenSSH ed25519 private key (`gitlab`, `gitlab.pub` with comment `testm@DESKTOP-PO28IS1`), which appears to be accidental author inclusion and is noted separately. ## Source: ghsa-malware (1f6d9ad8459443d96933ca9fbd388fa9dc5c596691af976cc8e7fce4bdd2727a) 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

Full system compromise on any computer with the polytrade package installed or running. Potential exposure and theft of all stored secrets and keys. Persistence of malicious software beyond removal of the package is possible, increasing the risk of ongoing unauthorized access.

Defensive guidance

Immediately remove the polytrade package from all affected systems. Rotate all secrets and keys that were stored on the compromised machines, performing this rotation from a separate, trusted computer. Conduct a thorough investigation and remediation of the affected systems, as removing the package alone may not eliminate all malicious software introduced. Consider rebuilding or restoring systems from known good backups to ensure full eradication of the compromise.

Summary

The polytrade package in the npm ecosystem has been identified as containing malicious code that grants full control of the infected computer to an outside entity. This level of compromise means that any sensitive information, including secrets and keys stored on the system, is at risk. The advisory warns that simply uninstalling the package may not remove all malicious components, indicating persistence mechanisms or additional payloads may be involved. There is no CVSS score or detailed technical vulnerability description available, but the severity is implied by the total system compromise statement.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2026, 13:52 UTC

Technical details

References

Community reviews