Malicious code in @polymarkets/clob-client-v2 (npm)
The npm package @polymarkets/clob-client-v2 version 1.0.6 contains malicious code due to a dependency on an inquirer package fetched from a lookalike registry URL (registrynpmjs.to) instead of the official npm registry. This typosquatting tactic allows the attacker controlling the fake registry to execute arbitrary code during installation or when the inquirer module is first required.
AI Analysis
Technical Summary
The package.json of @polymarkets/[email protected] declares its inquirer dependency as an HTTPS tarball URL pointing to registrynpmjs.to, a domain impersonating the official npm registry. When npm installs this package, it fetches the inquirer tarball from the malicious host, enabling the attacker to control code execution during the install lifecycle and on module import. The package is published under the scope @polymarkets, a one-character variation of the legitimate @polymarket scope, indicating a typosquatting attack vector designed to lure users into installing a malicious package.
Potential Impact
Users installing @polymarkets/[email protected] may unknowingly execute malicious code controlled by the attacker during installation or runtime due to the compromised inquirer dependency fetched from a fake registry. This can lead to arbitrary code execution within the environment where the package is installed.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing @polymarkets/[email protected] and verify dependencies to ensure they are fetched from legitimate sources. Check for updates or advisories from the package maintainers or npm registry. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Malicious code in @polymarkets/clob-client-v2 (npm)
Description
The npm package @polymarkets/clob-client-v2 version 1.0.6 contains malicious code due to a dependency on an inquirer package fetched from a lookalike registry URL (registrynpmjs.to) instead of the official npm registry. This typosquatting tactic allows the attacker controlling the fake registry to execute arbitrary code during installation or when the inquirer module is first required.
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 package.json of @polymarkets/[email protected] declares its inquirer dependency as an HTTPS tarball URL pointing to registrynpmjs.to, a domain impersonating the official npm registry. When npm installs this package, it fetches the inquirer tarball from the malicious host, enabling the attacker to control code execution during the install lifecycle and on module import. The package is published under the scope @polymarkets, a one-character variation of the legitimate @polymarket scope, indicating a typosquatting attack vector designed to lure users into installing a malicious package.
Potential Impact
Users installing @polymarkets/[email protected] may unknowingly execute malicious code controlled by the attacker during installation or runtime due to the compromised inquirer dependency fetched from a fake registry. This can lead to arbitrary code execution within the environment where the package is installed.
Mitigation Recommendations
No official patch or remediation is currently documented. Users should avoid installing @polymarkets/[email protected] and verify dependencies to ensure they are fetched from legitimate sources. Check for updates or advisories from the package maintainers or npm registry. 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-14050
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a7ff5f5bf8831d539880049
Added to database: 08/15/2026, 05:15:33 UTC
Last enriched: 08/15/2026, 05:42:56 UTC
Last updated: 08/15/2026, 10:38:13 UTC
Views: 6
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.