Malware in polymarket-trading-developer-tool
Malware was discovered in the npm package polymarket-trading-developer-tool. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- polymarket-trading-developer-tool
A malicious package named polymarket-trading-developer-tool was published to npm and contains malware that compromises any system on which it is installed or executed.\n\nAccording to the GitHub Advisory (GHSA-qh4r-g8mr-v3xp), any computer running this package should be considered fully compromised. The malware provides outside entities with full control of the affected system.\n\nImmediate remediation requires rotating all secrets and keys from a different, uncompromised computer, and removing the package. However, due to the level of system compromise, removal of the package alone may not eliminate all malicious software that was installed.\n\nThe advisory was published on 2026-08-21.
Indicators of compromise
- Packages
- polymarket-trading-developer-tool
Remediation
- Immediately remove the polymarket-trading-developer-tool package from all systems
- Rotate all secrets, API keys, credentials, and authentication tokens from a clean, uncompromised computer
- Perform a full security audit and malware scan of any system that had the package installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if the package was installed on production or sensitive systems
Sources
- GitHub Advisory GHSA-qh4r-g8mr-v3xp · GitHub Advisory Database
Cite this entry
"Malware in polymarket-trading-developer-tool." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 21, 2026; last updated August 21, 2026. https://supplychainattack.org/incident/malware-in-polymarket-trading-developer-tool-1di4nr
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