Malicious code in polytrade (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5bb6b9a4e70c868e150f06160b187915bcdeb6c9c8f95095af4766dde92f96c5) [email protected] 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.
AI Analysis
Technical 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.
Potential 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.
Mitigation Recommendations
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.
Malicious code in polytrade (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5bb6b9a4e70c868e150f06160b187915bcdeb6c9c8f95095af4766dde92f96c5) [email protected] 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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
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.
Potential 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.
Mitigation Recommendations
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.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6939
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-r7mv-rcm7-x7m3"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4e4f0dc9d9e3dbe328e0ec
Added to database: 07/08/2026, 13:22:21 UTC
Last enriched: 07/08/2026, 13:52:14 UTC
Last updated: 07/29/2026, 19:23:06 UTC
Views: 72
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.