Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in @shopbop/api-models

Malware was discovered in the npm package @shopbop/api-models. Systems with this package installed or running are considered fully compromised and require immediate remediation.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • @shopbop/api-models

A malware incident was identified in the npm package @shopbop/api-models, published as GitHub Advisory GHSA-g6vr-6p3c-gj3x on June 29, 2026.\n\nAccording to the advisory, any computer with this package installed or running should be considered fully compromised. The malware grants outside entities full control of affected systems.\n\nImmediate remediation is required, including rotation of all secrets and keys from a separate, uncompromised computer. While the package should be removed, complete removal of all malicious software cannot be guaranteed due to the level of system compromise achieved.\n\nThe attack vector is a compromised package in the npm ecosystem.

Indicators of compromise

Packages
  • @shopbop/api-models

Remediation

  • Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
  • Remove the @shopbop/api-models package from all affected systems
  • Conduct a full security audit and forensic analysis of any system that had this package installed
  • Monitor affected systems for signs of persistent compromise or lateral movement
  • Consider rebuilding affected systems from clean media if full compromise is suspected

Sources

  1. GitHub Advisory GHSA-g6vr-6p3c-gj3x · GitHub Advisory Database

Cite this entry

"Malware in @shopbop/api-models." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-shopbop-api-models-11tth1

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