Malicious code in polymarket-kit (npm)
The polymarket-kit npm package version 2.4.1 contains malicious code masquerading as a Polymarket API SDK. Instead of legitimate functionality, it fetches remote JSON data and executes code from the 'credits' field via a Function constructor, enabling arbitrary code execution in the Node.js process. Additionally, the package inadvertently includes an OpenSSH ed25519 private key belonging to the author, which should be rotated. This backdoor allows remote code execution through a fetch-and-eval mechanism disguised under Polymarket branding.
AI Analysis
Technical Summary
The polymarket-kit package version 2.4.1 is a malicious npm package that pretends to be a Polymarket API SDK but contains no legitimate Polymarket functionality. Its exported getPlugin() helper fetches JSON from a remote URL and executes the 'credits' field content as code within the Node.js environment using a Function constructor with access to require, module, process, and Buffer globals. This design creates a remote fetch-and-eval backdoor, allowing arbitrary code execution controlled by the remote endpoint. The package also ships with an OpenSSH ed25519 private key belonging to the author, which poses a security risk if reused elsewhere and should be rotated. No official patch or remediation is indicated in the provided data.
Potential Impact
This malicious package enables remote attackers controlling the remote JSON endpoint to execute arbitrary code within the Node.js process of any system that installs and runs polymarket-kit version 2.4.1. This can lead to full compromise of the host environment. The inclusion of a private SSH key in the package increases risk if the key is reused or not rotated, potentially allowing unauthorized access to systems where the key is trusted.
Mitigation Recommendations
No official patch or remediation is currently indicated. Users should avoid installing polymarket-kit version 2.4.1 and remove it if already present. The maintainer should rotate the exposed OpenSSH private key immediately. Monitor for any updates or advisories from the package maintainer or npm registry regarding this issue. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Malicious code in polymarket-kit (npm)
Description
The polymarket-kit npm package version 2.4.1 contains malicious code masquerading as a Polymarket API SDK. Instead of legitimate functionality, it fetches remote JSON data and executes code from the 'credits' field via a Function constructor, enabling arbitrary code execution in the Node.js process. Additionally, the package inadvertently includes an OpenSSH ed25519 private key belonging to the author, which should be rotated. This backdoor allows remote code execution through a fetch-and-eval mechanism disguised under Polymarket branding.
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 polymarket-kit package version 2.4.1 is a malicious npm package that pretends to be a Polymarket API SDK but contains no legitimate Polymarket functionality. Its exported getPlugin() helper fetches JSON from a remote URL and executes the 'credits' field content as code within the Node.js environment using a Function constructor with access to require, module, process, and Buffer globals. This design creates a remote fetch-and-eval backdoor, allowing arbitrary code execution controlled by the remote endpoint. The package also ships with an OpenSSH ed25519 private key belonging to the author, which poses a security risk if reused elsewhere and should be rotated. No official patch or remediation is indicated in the provided data.
Potential Impact
This malicious package enables remote attackers controlling the remote JSON endpoint to execute arbitrary code within the Node.js process of any system that installs and runs polymarket-kit version 2.4.1. This can lead to full compromise of the host environment. The inclusion of a private SSH key in the package increases risk if the key is reused or not rotated, potentially allowing unauthorized access to systems where the key is trusted.
Mitigation Recommendations
No official patch or remediation is currently indicated. Users should avoid installing polymarket-kit version 2.4.1 and remove it if already present. The maintainer should rotate the exposed OpenSSH private key immediately. Monitor for any updates or advisories from the package maintainer or npm registry regarding this issue. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10071
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a50baaa68715ace435855fa
Added to database: 07/10/2026, 09:26:02 UTC
Last enriched: 07/10/2026, 10:16:46 UTC
Last updated: 07/30/2026, 22:55:48 UTC
Views: 61
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.