Malicious code in polymarket-trading-developer-tool (npm)
The polymarket-trading-developer-tool npm package versions 0.1.1 and 0.1.2 contain malicious code that executes arbitrary JavaScript during installation. Its postinstall script downloads and runs attacker-controlled code from a mutable remote URL without integrity or signature verification, enabling install-time remote code execution. The package masquerades as a legitimate developer tool, but its installation process can compromise the installer's machine.
AI Analysis
Technical Summary
The polymarket-trading-developer-tool npm package (versions 0.1.1 and 0.1.2) includes a postinstall lifecycle script that performs install-time remote code execution. It fetches a JSON configuration from a mutable endpoint (pm-trading-dev-tools-be.vercel.app/config/clob-math.json) which specifies a URL to a .tgz archive. This archive is downloaded, extracted, and installed with npm install --omit=dev, executing any lifecycle scripts of transitive dependencies. Subsequently, it requires and executes a function from the fetched code in-process. There is no integrity check, version pinning, or signature verification, allowing an attacker to control the code executed during installation. The package's legitimate-appearing code serves as a cover for this malicious behavior.
Potential Impact
This vulnerability allows an attacker to execute arbitrary code on the machine of anyone installing the affected package versions. Because the postinstall script downloads and runs code from a mutable remote source without verification, attackers can change the payload at any time to deliver malicious JavaScript, potentially leading to full system compromise or further attacks on the environment where the package is installed.
Mitigation Recommendations
No official patch or fix is currently available. Users should avoid installing polymarket-trading-developer-tool versions 0.1.1 and 0.1.2. Since the package fetches code from a mutable remote source without integrity checks, there is no reliable mitigation other than not using these versions. Monitor for updates from the package maintainers or security advisories for any official remediation.
Malicious code in polymarket-trading-developer-tool (npm)
Description
The polymarket-trading-developer-tool npm package versions 0.1.1 and 0.1.2 contain malicious code that executes arbitrary JavaScript during installation. Its postinstall script downloads and runs attacker-controlled code from a mutable remote URL without integrity or signature verification, enabling install-time remote code execution. The package masquerades as a legitimate developer tool, but its installation process can compromise the installer's machine.
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-trading-developer-tool npm package (versions 0.1.1 and 0.1.2) includes a postinstall lifecycle script that performs install-time remote code execution. It fetches a JSON configuration from a mutable endpoint (pm-trading-dev-tools-be.vercel.app/config/clob-math.json) which specifies a URL to a .tgz archive. This archive is downloaded, extracted, and installed with npm install --omit=dev, executing any lifecycle scripts of transitive dependencies. Subsequently, it requires and executes a function from the fetched code in-process. There is no integrity check, version pinning, or signature verification, allowing an attacker to control the code executed during installation. The package's legitimate-appearing code serves as a cover for this malicious behavior.
Potential Impact
This vulnerability allows an attacker to execute arbitrary code on the machine of anyone installing the affected package versions. Because the postinstall script downloads and runs code from a mutable remote source without verification, attackers can change the payload at any time to deliver malicious JavaScript, potentially leading to full system compromise or further attacks on the environment where the package is installed.
Mitigation Recommendations
No official patch or fix is currently available. Users should avoid installing polymarket-trading-developer-tool versions 0.1.1 and 0.1.2. Since the package fetches code from a mutable remote source without integrity checks, there is no reliable mitigation other than not using these versions. Monitor for updates from the package maintainers or security advisories for any official remediation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6714
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a50ba9168715ace435822fb
Added to database: 07/10/2026, 09:25:37 UTC
Last enriched: 07/10/2026, 10:09:07 UTC
Last updated: 07/26/2026, 22:09:59 UTC
Views: 27
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.