Malicious code in polymarket-trade (npm)
A coordinated supply-chain attack involving nine npm packages published by the maintainer polymarketdev impersonates legitimate Polymarket trading tools. These packages exfiltrate Ethereum private keys by prompting users interactively or silently reading environment variables, then sending the keys to a malicious Cloudflare Worker endpoint. The malicious code persists locally and fingerprints infected devices. The attack targets developers and traders using Polymarket-related packages, exploiting trust in package provenance. The packages include polymarket-trade version 0.1.0 and others with identical malicious payloads.
AI Analysis
Technical Summary
This threat is a supply-chain attack where nine npm packages published by the maintainer polymarketdev (GitHub actor texsellix) masquerade as Polymarket CLOB trading tools. The packages contain a malicious postinstall script that detects interactive terminals to prompt users for Ethereum private keys or silently reads PRIVATE_KEY environment variables from .env files. The stolen keys are exfiltrated via HTTPS POST requests to a Cloudflare Worker endpoint controlled by the attacker. The packages create local persistence files for device fingerprinting and track exfiltration timestamps. The malicious payload is identical across all packages except for the package name. The attack targets developers using Polymarket-related packages, including polymarket-trade version 0.1.0, aiming to steal private keys controlling real USDC and Polymarket positions.
Potential Impact
Compromise of Ethereum private keys allows attackers to fully control victims' Polygon wallets, enabling theft of USDC and manipulation of Polymarket positions. Any system installing these packages is considered fully compromised, with all secrets and keys at risk. The attacker gains persistent device fingerprinting and can track stolen keys over time. The malicious packages deceive users by providing legitimate trading functionality as cover, increasing the likelihood of key theft.
Mitigation Recommendations
No official patch or fix is currently available. Users should immediately remove these malicious packages and consider all secrets and keys stored on affected systems compromised. Rotate all Ethereum private keys from a secure, uncompromised environment. Avoid installing packages from untrusted or unknown maintainers, especially those related to Polymarket trading. Monitor for suspicious postinstall scripts in npm packages and verify package provenance before installation.
Malicious code in polymarket-trade (npm)
Description
A coordinated supply-chain attack involving nine npm packages published by the maintainer polymarketdev impersonates legitimate Polymarket trading tools. These packages exfiltrate Ethereum private keys by prompting users interactively or silently reading environment variables, then sending the keys to a malicious Cloudflare Worker endpoint. The malicious code persists locally and fingerprints infected devices. The attack targets developers and traders using Polymarket-related packages, exploiting trust in package provenance. The packages include polymarket-trade version 0.1.0 and others with identical malicious payloads.
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
This threat is a supply-chain attack where nine npm packages published by the maintainer polymarketdev (GitHub actor texsellix) masquerade as Polymarket CLOB trading tools. The packages contain a malicious postinstall script that detects interactive terminals to prompt users for Ethereum private keys or silently reads PRIVATE_KEY environment variables from .env files. The stolen keys are exfiltrated via HTTPS POST requests to a Cloudflare Worker endpoint controlled by the attacker. The packages create local persistence files for device fingerprinting and track exfiltration timestamps. The malicious payload is identical across all packages except for the package name. The attack targets developers using Polymarket-related packages, including polymarket-trade version 0.1.0, aiming to steal private keys controlling real USDC and Polymarket positions.
Potential Impact
Compromise of Ethereum private keys allows attackers to fully control victims' Polygon wallets, enabling theft of USDC and manipulation of Polymarket positions. Any system installing these packages is considered fully compromised, with all secrets and keys at risk. The attacker gains persistent device fingerprinting and can track stolen keys over time. The malicious packages deceive users by providing legitimate trading functionality as cover, increasing the likelihood of key theft.
Mitigation Recommendations
No official patch or fix is currently available. Users should immediately remove these malicious packages and consider all secrets and keys stored on affected systems compromised. Rotate all Ethereum private keys from a secure, uncompromised environment. Avoid installing packages from untrusted or unknown maintainers, especially those related to Polymarket trading. Monitor for suspicious postinstall scripts in npm packages and verify package provenance before installation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-4215
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-5qjv-f5g4-jx7w"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a885f21acd9273b493f7d3d
Added to database: 08/21/2026, 14:22:25 UTC
Last enriched: 08/21/2026, 14:31:25 UTC
Last updated: 08/22/2026, 03:51:58 UTC
Views: 4
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.