Malicious code in polymarket-auto-trade (npm)
A coordinated supply-chain attack involving nine npm packages published by the maintainer polymarketdev that masquerade as legitimate Polymarket trading tools. These packages exfiltrate Ethereum private keys from infected systems to a Cloudflare Worker command-and-control server. The malicious code uses a postinstall hook to evade automated detection and steals private keys either by prompting the user or silently reading environment variables. It also establishes local persistence and fingerprints infected devices. The packages include legitimate dependencies and provide functional trading commands as a cover for the credential theft.
AI Analysis
Technical Summary
This threat is a supply-chain attack targeting npm packages published by the maintainer polymarketdev (GitHub actor texsellix). Nine packages, including polymarket-auto-trade, were published within a two-minute window and contain identical malicious payloads in their dist/index.js file. The payload wraps legitimate Polymarket CLOB SDK and other libraries to appear functional while exfiltrating Ethereum private keys to a Cloudflare Worker C2 endpoint. The postinstall script detects interactive shells to selectively prompt for private keys or silently steal them from .env files. It creates local persistence files with device and wallet fingerprints and sends stolen keys with device identifiers over HTTPS. The campaign targets developers using LLM-assisted coding workflows and trade automation tools, exploiting trust in these packages.
Potential Impact
Any system that installs or runs these malicious packages is considered fully compromised. Ethereum private keys stored or entered on the infected system are exfiltrated to an attacker-controlled server, resulting in loss of control over associated cryptocurrency assets. Because the malware establishes local persistence and fingerprints devices, attackers may maintain ongoing access. The presence of these packages in development environments risks widespread credential theft and financial loss. Removing the package alone does not guarantee full remediation due to potential additional malware installed.
Mitigation Recommendations
Immediate removal of all affected packages is required. All Ethereum private keys and secrets stored or used on the compromised system must be rotated immediately from a separate, secure environment. Because the malware establishes persistence and may have granted full system control to attackers, a full system compromise should be assumed. Reinstalling the operating system or restoring from a known clean backup is recommended. Developers should verify package provenance carefully and avoid installing untrusted or unknown npm packages, especially those published in rapid succession by the same maintainer. Monitor official advisories for updates.
Malicious code in polymarket-auto-trade (npm)
Description
A coordinated supply-chain attack involving nine npm packages published by the maintainer polymarketdev that masquerade as legitimate Polymarket trading tools. These packages exfiltrate Ethereum private keys from infected systems to a Cloudflare Worker command-and-control server. The malicious code uses a postinstall hook to evade automated detection and steals private keys either by prompting the user or silently reading environment variables. It also establishes local persistence and fingerprints infected devices. The packages include legitimate dependencies and provide functional trading commands as a cover for the credential theft.
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 npm packages published by the maintainer polymarketdev (GitHub actor texsellix). Nine packages, including polymarket-auto-trade, were published within a two-minute window and contain identical malicious payloads in their dist/index.js file. The payload wraps legitimate Polymarket CLOB SDK and other libraries to appear functional while exfiltrating Ethereum private keys to a Cloudflare Worker C2 endpoint. The postinstall script detects interactive shells to selectively prompt for private keys or silently steal them from .env files. It creates local persistence files with device and wallet fingerprints and sends stolen keys with device identifiers over HTTPS. The campaign targets developers using LLM-assisted coding workflows and trade automation tools, exploiting trust in these packages.
Potential Impact
Any system that installs or runs these malicious packages is considered fully compromised. Ethereum private keys stored or entered on the infected system are exfiltrated to an attacker-controlled server, resulting in loss of control over associated cryptocurrency assets. Because the malware establishes local persistence and fingerprints devices, attackers may maintain ongoing access. The presence of these packages in development environments risks widespread credential theft and financial loss. Removing the package alone does not guarantee full remediation due to potential additional malware installed.
Defensive Guidance
Immediate removal of all affected packages is required. All Ethereum private keys and secrets stored or used on the compromised system must be rotated immediately from a separate, secure environment. Because the malware establishes persistence and may have granted full system control to attackers, a full system compromise should be assumed. Reinstalling the operating system or restoring from a known clean backup is recommended. Developers should verify package provenance carefully and avoid installing untrusted or unknown npm packages, especially those published in rapid succession by the same maintainer. Monitor official advisories for updates.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-4210
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-3j8p-hfj4-j6w6"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a885f21acd9273b493f7d4d
Added to database: 08/21/2026, 14:22:25 UTC
Last enriched: 08/21/2026, 14:32:34 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.