Malware in polymarket-trade
The npm package polymarket-trade was found to contain malware. Any computer with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different system.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- polymarket-tradenpm package containing malware
The npm package polymarket-trade was identified as containing malware and published to the npm registry. GitHub Security Advisory GHSA-5qjv-f5g4-jx7w documents the incident.\n\nSystems with this package installed or running are considered fully compromised. The advisory recommends immediate rotation of all secrets and keys from a different, unaffected computer. While the package should be removed, complete remediation cannot be guaranteed due to the potential for the malware to have granted outside entities full control of the affected system.\n\nThis represents a critical supply chain compromise affecting any developer or system that installed or executed this package.
Indicators of compromise
- Packages
- polymarket-trade
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, unaffected computer
- Remove the polymarket-trade package from all affected systems
- Audit system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider the affected system(s) potentially compromised and plan for full rebuild or forensic analysis
- Check for any other suspicious packages or modifications on affected systems
- Notify any services that may have had credentials stored on the affected system
Sources
- GitHub Advisory GHSA-5qjv-f5g4-jx7w · GitHub Advisory Database
Cite this entry
"Malware in polymarket-trade." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 21, 2026; last updated August 21, 2026. https://supplychainattack.org/incident/malware-in-polymarket-trade-19rswx
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in svelte-dim-kit
The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.
npmCompromised package - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in stillm4ddpocs-rtest-bravo (npm)
The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.
npmCompromised package