Malware in polymarket-onchain-sdk
Malware was discovered in the polymarket-onchain-sdk npm package. Systems with the package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- polymarket-onchain-sdknpm package
The polymarket-onchain-sdk npm package was found to contain malware. According to the advisory, any computer with this package installed or running should be considered fully compromised, with all secrets and keys potentially exposed to an outside entity.\n\nThe malware grants full control of affected systems to an external threat actor. While removing the package is recommended, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise.\n\nAffected users should immediately rotate all secrets and keys from a different, uncompromised computer and remove the package from their systems.
Indicators of compromise
- Packages
- polymarket-onchain-sdk
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the polymarket-onchain-sdk package from all affected systems
- Audit system logs for unauthorized access or activity
- Consider full system reimaging if the package was installed on production or sensitive systems
- Review and revoke any API tokens or authentication credentials that may have been exposed
Sources
- GitHub Advisory GHSA-89w2-qgj2-9f2w · GitHub Advisory Database
Cite this entry
"Malware in polymarket-onchain-sdk." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-polymarket-onchain-sdk-fwajsn
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in testingsmthb1g (npm)
The npm package testingsmthb1g contains malicious code in its postinstall script that acts as an install-time dropper, downloading and executing a Windows binary payload and exfiltrating platform information. The attack includes sandbox escape capabilities for WSL/virtualized Linux environments.
npmCompromised package - resolvedcritical
Malicious code in mutex-core (npm)
The npm package mutex-core, published under a name resembling the popular async-mutex library, contained malicious code including a staged loader that decrypts and executes hidden payloads. The package included obfuscated code that conditionally triggers AES-256-GCM decryption and execution of encrypted binary content when specific conditions are met.
npmCompromised package - containedcritical
Malicious code in tyepescript-cli (npm)
tyepescript-cli, a typosquat of the legitimate typescript package on npm, contains malicious postinstall code that downloads and executes a Windows binary (main.exe) and beacons to an attacker-controlled server. The package uses XOR obfuscation to hide URLs, commands, and IP addresses, with special logic to target both Windows and WSL environments.
npmTyposquattingCompromised package - containedcritical
Malicious code in commandor-cli (npm)
commandor-cli@1.0.0 on npm contains malicious postinstall script that downloads and executes a binary from an attacker-controlled GitHub repository. The script also beacons installation metadata to a command-and-control server and includes a PowerShell bridge to extend execution to Windows hosts on WSL systems.
npmCompromised packageMalicious commit