Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in bigops-storio

Malware was discovered in the npm package bigops-storio. Systems with this package installed or running should be 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
  • bigops-storio

The npm package bigops-storio was found to contain malware. According to the GitHub advisory (GHSA-g548-9c3x-q2r5), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated from a different, uncompromised system. The package should be removed, though complete removal of all malicious software cannot be guaranteed given the potential for full system compromise.\n\nThis is a critical supply chain incident affecting the npm ecosystem, with the potential for widespread impact on any developer or system that installed or executed this package.

Indicators of compromise

Packages
  • bigops-storio

Remediation

  • Immediately remove the bigops-storio package from all systems
  • Rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Perform a full security audit and malware scan of any affected systems
  • Review system logs and network activity for signs of unauthorized access or data exfiltration
  • Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical infrastructure

Sources

  1. GitHub Advisory GHSA-g548-9c3x-q2r5 · GitHub Advisory Database

Cite this entry

"Malware in bigops-storio." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malware-in-bigops-storio-yiv71q

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