Malicious code in polymarket-copy-trading (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 or silently reading environment variables and send them to a malicious Cloudflare Worker C2 endpoint. The malicious code uses a postinstall hook that evades automated analysis by detecting interactive shells and only prompting for keys in interactive sessions. The packages maintain local persistence and fingerprint infected devices. The attacker gains full control over compromised wallets, enabling theft of on-chain assets. The campaign targets developers using LLM-assisted coding workflows and those seeking copy-trading tools. The affected package version is 0.1.0. No official patch is available, and removal alone may not fully remediate the compromise.
AI Analysis
Technical Summary
This threat is a supply-chain attack comprising nine npm packages published within a short time window by the polymarketdev maintainer. Each package contains identical malicious code that wraps legitimate Polymarket SDK functionality to appear authentic while stealing Ethereum private keys. The postinstall script probes for interactive terminals to evade automated scanners and prompts users to input private keys or silently extracts keys from .env files. Stolen keys are exfiltrated via HTTPS POST requests to a Cloudflare Workers subdomain impersonating Polymarket infrastructure. The packages create local files for persistence and device fingerprinting. Metadata inconsistencies and typosquatting domains confirm the malicious intent. Installing and interacting with these packages compromises wallet security, allowing attackers to drain assets. The affected version explicitly identified is 0.1.0.
Potential Impact
Users who install and interact with these malicious npm packages risk full compromise of their Ethereum wallets. The attacker obtains plaintext private keys, enabling complete control over the wallets, including the ability to drain USDC, CTF positions, and other on-chain assets. The malware also establishes local persistence and device fingerprinting, indicating potential ongoing compromise. Because the exfiltration endpoint is external and impersonates legitimate infrastructure, victims may not detect the theft. The compromise extends beyond the package itself, as attackers may have gained broader access to the infected system.
Mitigation Recommendations
No official patch or fix is currently available for these malicious packages. Users should immediately remove the affected packages (version =0.1.0) from their environments. All Ethereum private keys and secrets that may have been exposed must be rotated from a secure, uncompromised device. Due to the potential for full system compromise, affected systems should be considered untrusted, and a full security assessment and remediation should be performed. Avoid installing npm packages from unverified sources, especially those impersonating legitimate tooling. Monitor vendor advisories for any updates or official remediation guidance.
Malicious code in polymarket-copy-trading (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 or silently reading environment variables and send them to a malicious Cloudflare Worker C2 endpoint. The malicious code uses a postinstall hook that evades automated analysis by detecting interactive shells and only prompting for keys in interactive sessions. The packages maintain local persistence and fingerprint infected devices. The attacker gains full control over compromised wallets, enabling theft of on-chain assets. The campaign targets developers using LLM-assisted coding workflows and those seeking copy-trading tools. The affected package version is 0.1.0. No official patch is available, and removal alone may not fully remediate the compromise.
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 comprising nine npm packages published within a short time window by the polymarketdev maintainer. Each package contains identical malicious code that wraps legitimate Polymarket SDK functionality to appear authentic while stealing Ethereum private keys. The postinstall script probes for interactive terminals to evade automated scanners and prompts users to input private keys or silently extracts keys from .env files. Stolen keys are exfiltrated via HTTPS POST requests to a Cloudflare Workers subdomain impersonating Polymarket infrastructure. The packages create local files for persistence and device fingerprinting. Metadata inconsistencies and typosquatting domains confirm the malicious intent. Installing and interacting with these packages compromises wallet security, allowing attackers to drain assets. The affected version explicitly identified is 0.1.0.
Potential Impact
Users who install and interact with these malicious npm packages risk full compromise of their Ethereum wallets. The attacker obtains plaintext private keys, enabling complete control over the wallets, including the ability to drain USDC, CTF positions, and other on-chain assets. The malware also establishes local persistence and device fingerprinting, indicating potential ongoing compromise. Because the exfiltration endpoint is external and impersonates legitimate infrastructure, victims may not detect the theft. The compromise extends beyond the package itself, as attackers may have gained broader access to the infected system.
Defensive Guidance
No official patch or fix is currently available for these malicious packages. Users should immediately remove the affected packages (version =0.1.0) from their environments. All Ethereum private keys and secrets that may have been exposed must be rotated from a secure, uncompromised device. Due to the potential for full system compromise, affected systems should be considered untrusted, and a full security assessment and remediation should be performed. Avoid installing npm packages from unverified sources, especially those impersonating legitimate tooling. Monitor vendor advisories for any updates or official remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-4213
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-9jh7-4779-9m8r"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a885f21acd9273b493f7d41
Added to database: 08/21/2026, 14:22:25 UTC
Last enriched: 08/21/2026, 14:32:00 UTC
Last updated: 08/22/2026, 03:51:58 UTC
Views: 2
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.