Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in polymarket-trader-apis

Malware was discovered in the npm package polymarket-trader-apis. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • polymarket-trader-apisnpm package containing malware

The npm package polymarket-trader-apis was found to contain malware. According to the GitHub Advisory (GHSA-773r-gj6w-h338), any computer with this package installed or running should be considered fully compromised.\n\nImmediate action is required: all secrets and keys stored on affected computers must be rotated immediately from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the compromise.\n\nThe advisory was published on 2026-07-10 via the GitHub Advisory Database.

Indicators of compromise

Packages
  • polymarket-trader-apis

Remediation

  • Immediately rotate all secrets and keys from a different, uncompromised computer
  • Remove the polymarket-trader-apis package from all affected systems
  • Conduct a full security audit of any system that had this package installed
  • Monitor affected systems for signs of unauthorized access or persistence mechanisms
  • Consider full system reimaging if complete compromise is suspected

Sources

  1. GitHub Advisory GHSA-773r-gj6w-h338 · GitHub Advisory Database

Cite this entry

"Malware in polymarket-trader-apis." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 10, 2026; last updated July 10, 2026. https://supplychainattack.org/incident/malware-in-polymarket-trader-apis-1kpuip

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. resolvedcritical

    Malicious code in sme-rko-finance-front-operations-feed-models (npm)

    The npm package sme-rko-finance-front-operations-feed-models contained malicious code that downloads and executes attacker-controlled native binaries from remote servers upon package load. The malware uses obfuscation techniques including fragmented string arrays, platform-specific endpoints, and DNS TXT record fallbacks to evade detection.

    npmCompromised package
  2. resolvedcritical

    Malicious code in modern-localization (npm)

    The npm package modern-localization contained malicious code that fetches and executes arbitrary JavaScript from a remote jsonbin.io endpoint on server-side require, with no integrity verification. The payload is executed with full Node.js privileges via Function() or child_process.fork().

    npmCompromised package
  3. resolvedcritical

    Malicious code in sme-rko-finance-front-operations-tax (npm)

    The npm package sme-rko-finance-front-operations-tax contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure on require. The package was identified and reported by OpenSSF's malicious-packages project.

    npmCompromised package
  4. resolvedcritical

    Malicious code in localization-fixer (npm)

    The npm package localization-fixer contained malicious code that fetches and executes arbitrary JavaScript from attacker-controlled jsonbin.io endpoints on package require, granting full Node.js capabilities to remote payloads.

    npmCompromised package