Malicious code in polymarket-bot-logger (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (16019aad4a4500c2df862c6b811c97b0fe227673fd10d921a453924410d17948) On npm install, the package's postinstall hook runs install-check.cjs, which fetches a JSON config from https://jipred.vercel.app/config/clob-math.json (also overridable via the PSM_PEER_URL env var), reads a peerBundle/bundle URL from that JSON, downloads a.tgz to a.peer/ directory, runs npm install inside it, then require()s peer-math.js and invokes syncSession(). The fetched bundle is unpinned, unverified (no hash or signature check), and served from a mutable non-registry, non-publisher Vercel host, so the code executed on the installer's machine is fully controlled by whoever operates jipred.vercel.app at install time. The package.json name (polymarket-bot-logger, self-described as a logging library) also does not match the README (polymarket-stake-math, a Kelly stake-sizing math library) or the postinstall log tag ([polymarket-stake-math]), and neither declared purpose requires downloading and executing a remote code bundle at install time. ## Source: ghsa-malware (f87cf236471990681e6705f98e5270bcd5212aea8b69b33f071b45eeb18b4449) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
AI Analysis
Technical Summary
The polymarket-bot-logger npm package (version 1.0.1) executes a postinstall hook that fetches a JSON configuration from a mutable, non-registry Vercel-hosted URL. This configuration points to a remote tgz bundle that is downloaded, installed, and executed without any integrity verification such as hashes or signatures. The remote code execution occurs during installation, granting the operator of the remote server full control over the installing machine. The package's metadata and README are inconsistent and do not require downloading or executing remote code, indicating malicious intent. This behavior effectively compromises any system installing this package.
Potential Impact
Any system that installs polymarket-bot-logger version 1.0.1 is fully compromised due to arbitrary remote code execution during installation. Attackers can gain complete control over the affected machine, potentially stealing secrets, keys, and other sensitive data. Removal of the package does not guarantee full remediation as the attacker may have already established persistence or installed additional malware.
Mitigation Recommendations
Remove the polymarket-bot-logger package immediately from all affected systems. Rotate all secrets, keys, and credentials that were stored or accessible on the compromised machines, using a clean, uncompromised environment. Do not trust the affected machines until fully rebuilt or verified clean. Avoid installing packages from untrusted sources or those that execute unverified remote code during installation.
Malicious code in polymarket-bot-logger (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (16019aad4a4500c2df862c6b811c97b0fe227673fd10d921a453924410d17948) On npm install, the package's postinstall hook runs install-check.cjs, which fetches a JSON config from https://jipred.vercel.app/config/clob-math.json (also overridable via the PSM_PEER_URL env var), reads a peerBundle/bundle URL from that JSON, downloads a.tgz to a.peer/ directory, runs npm install inside it, then require()s peer-math.js and invokes syncSession(). The fetched bundle is unpinned, unverified (no hash or signature check), and served from a mutable non-registry, non-publisher Vercel host, so the code executed on the installer's machine is fully controlled by whoever operates jipred.vercel.app at install time. The package.json name (polymarket-bot-logger, self-described as a logging library) also does not match the README (polymarket-stake-math, a Kelly stake-sizing math library) or the postinstall log tag ([polymarket-stake-math]), and neither declared purpose requires downloading and executing a remote code bundle at install time. ## Source: ghsa-malware (f87cf236471990681e6705f98e5270bcd5212aea8b69b33f071b45eeb18b4449) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
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
The polymarket-bot-logger npm package (version 1.0.1) executes a postinstall hook that fetches a JSON configuration from a mutable, non-registry Vercel-hosted URL. This configuration points to a remote tgz bundle that is downloaded, installed, and executed without any integrity verification such as hashes or signatures. The remote code execution occurs during installation, granting the operator of the remote server full control over the installing machine. The package's metadata and README are inconsistent and do not require downloading or executing remote code, indicating malicious intent. This behavior effectively compromises any system installing this package.
Potential Impact
Any system that installs polymarket-bot-logger version 1.0.1 is fully compromised due to arbitrary remote code execution during installation. Attackers can gain complete control over the affected machine, potentially stealing secrets, keys, and other sensitive data. Removal of the package does not guarantee full remediation as the attacker may have already established persistence or installed additional malware.
Mitigation Recommendations
Remove the polymarket-bot-logger package immediately from all affected systems. Rotate all secrets, keys, and credentials that were stored or accessible on the compromised machines, using a clean, uncompromised environment. Do not trust the affected machines until fully rebuilt or verified clean. Avoid installing packages from untrusted sources or those that execute unverified remote code during installation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10516
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a55ff8a68715ace432f4794
Added to database: 07/14/2026, 09:21:14 UTC
Last enriched: 08/21/2026, 16:59:27 UTC
Last updated: 09/07/2026, 19:26:17 UTC
Views: 31
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.