Malicious code in polymarket-trading-cli (npm)
A coordinated supply-chain attack involving nine npm packages published by the maintainer polymarketdev impersonates legitimate Polymarket trading tools. These malicious packages exfiltrate Ethereum private keys by prompting users or silently reading environment variables, then sending the keys to a Cloudflare Worker command-and-control server. The malware uses a postinstall hook to evade automated detection and maintains local persistence with device fingerprinting. The packages include working trading commands as cover and falsely claim private keys remain encrypted. Any system with these packages installed is considered fully compromised.
AI Analysis
Technical Summary
This threat is a supply-chain attack targeting developers using Polymarket-related npm packages published by the maintainer polymarketdev (GitHub actor texsellix). Within a short time window, nine packages were published that contain identical malicious code in dist/index.js. The postinstall script detects interactive terminals to prompt for Ethereum private keys or silently reads the PRIVATE_KEY environment variable from .env files. It persists locally by creating a hidden directory with device and wallet metadata and exfiltrates stolen keys via HTTPS POST requests to a Cloudflare Worker C2 endpoint, including a device fingerprint header. The packages wrap legitimate Polymarket CLOB SDK and related libraries to provide functional trading commands, misleading users about key security. The campaign targets developers using LLM-assisted coding workflows by naming packages to appear relevant and trustworthy.
Potential Impact
Systems with these malicious packages installed are fully compromised. Ethereum private keys stored in environment variables or entered interactively are stolen and sent to an attacker-controlled server, risking theft of cryptocurrency assets. The malware establishes local persistence and device fingerprinting, enabling ongoing unauthorized access. Removal of the packages does not guarantee full remediation due to potential additional malicious artifacts. Developers relying on these packages risk credential theft and subsequent asset loss.
Mitigation Recommendations
Immediate removal of all polymarketdev npm packages is required. All Ethereum private keys and related secrets stored on affected systems must be rotated immediately from a secure, uncompromised environment. Due to the potential for full system compromise, consider rebuilding affected systems. Monitor for any unauthorized transactions or access to Ethereum wallets associated with compromised keys. No official patch or fix is available; remediation relies on removal and secret rotation.
Malicious code in polymarket-trading-cli (npm)
Description
A coordinated supply-chain attack involving nine npm packages published by the maintainer polymarketdev impersonates legitimate Polymarket trading tools. These malicious packages exfiltrate Ethereum private keys by prompting users or silently reading environment variables, then sending the keys to a Cloudflare Worker command-and-control server. The malware uses a postinstall hook to evade automated detection and maintains local persistence with device fingerprinting. The packages include working trading commands as cover and falsely claim private keys remain encrypted. Any system with these packages installed is considered fully compromised.
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 targeting developers using Polymarket-related npm packages published by the maintainer polymarketdev (GitHub actor texsellix). Within a short time window, nine packages were published that contain identical malicious code in dist/index.js. The postinstall script detects interactive terminals to prompt for Ethereum private keys or silently reads the PRIVATE_KEY environment variable from .env files. It persists locally by creating a hidden directory with device and wallet metadata and exfiltrates stolen keys via HTTPS POST requests to a Cloudflare Worker C2 endpoint, including a device fingerprint header. The packages wrap legitimate Polymarket CLOB SDK and related libraries to provide functional trading commands, misleading users about key security. The campaign targets developers using LLM-assisted coding workflows by naming packages to appear relevant and trustworthy.
Potential Impact
Systems with these malicious packages installed are fully compromised. Ethereum private keys stored in environment variables or entered interactively are stolen and sent to an attacker-controlled server, risking theft of cryptocurrency assets. The malware establishes local persistence and device fingerprinting, enabling ongoing unauthorized access. Removal of the packages does not guarantee full remediation due to potential additional malicious artifacts. Developers relying on these packages risk credential theft and subsequent asset loss.
Defensive Guidance
Immediate removal of all polymarketdev npm packages is required. All Ethereum private keys and related secrets stored on affected systems must be rotated immediately from a secure, uncompromised environment. Due to the potential for full system compromise, consider rebuilding affected systems. Monitor for any unauthorized transactions or access to Ethereum wallets associated with compromised keys. No official patch or fix is available; remediation relies on removal and secret rotation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-4217
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-q888-mwhg-ccmp"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a885f20acd9273b493f7d1d
Added to database: 08/21/2026, 14:22:24 UTC
Last enriched: 08/21/2026, 14:31:02 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.