Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in poly-provider-api

Malware was discovered in the npm package poly-provider-api. 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
  • poly-provider-api

A critical malware incident was identified in the npm package poly-provider-api. According to the GitHub Advisory (GHSA-jxxm-5453-r666), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software that resulted from the installation.\n\nThis represents a critical supply chain compromise affecting npm ecosystem users.

Indicators of compromise

Packages
  • poly-provider-api

Remediation

  • Immediately rotate all secrets and keys from a different, uncompromised computer
  • Remove the poly-provider-api 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
  • Review and revoke any credentials or API keys that may have been exposed

Sources

  1. GitHub Advisory GHSA-jxxm-5453-r666 · GitHub Advisory Database

Cite this entry

"Malware in poly-provider-api." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malware-in-poly-provider-api-1yc4xe

Suggest a correction

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

  1. containedcritical

    Malware in fetch-runtime

    Malware was discovered in the npm package fetch-runtime. Any system with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.

    npmCompromised package
  2. resolvedcritical

    Malicious code in ghazaly (npm)

    The npm package ghazaly version 99.9.0 contained malicious code that executed a postinstall hook to collect system information (hostname, current user, IP addresses) and exfiltrate it to a Burp Collaborator domain. The package exhibited dependency-confusion characteristics with a high version number and nonsense dependencies.

    npmCompromised packageDependency confusion
  3. containedcritical

    Malicious code in base65-13x (npm)

    base65-13x@5.0.2 on npm contains malicious obfuscated code disguised as a legitimate base-x library. The decode() function executes a ~123KB VM-style payload with dynamic code construction and network I/O capabilities.

    npmCompromised package
  4. containedcritical

    Malicious code in kit-vim-map (npm)

    The npm package kit-vim-map contained malicious code that executes a remote-controlled Linux ELF binary on installation, providing the attacker with arbitrary RCE, persistence, and file exfiltration capabilities. The binary beacons to C2 server 217.60.77.63 and establishes persistence via systemd user units.

    npmCompromised packageMalicious commit