Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in nbmolviz-js

Malware was discovered in the npm package nbmolviz-js. Systems with this package installed are considered fully compromised and require immediate remediation including secret rotation and package removal.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with nbmolviz-js installed or running
Ecosystems
Attack vectors
Affected entities
  • nbmolviz-js

A critical malware incident was identified in the npm package nbmolviz-js. According to the GitHub Advisory (GHSA-fc4r-p4fh-6h4p), 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 severe supply chain compromise affecting npm ecosystem users who installed the affected package.

Indicators of compromise

Packages
  • nbmolviz-js

Remediation

  • Immediately rotate all secrets and keys from a different, uncompromised computer
  • Remove the nbmolviz-js package from all affected systems
  • Conduct a full security audit of any system that had nbmolviz-js installed
  • Monitor affected systems for signs of unauthorized access or persistence mechanisms
  • Consider the affected system potentially compromised and plan for full remediation or replacement

Sources

  1. GitHub Advisory GHSA-fc4r-p4fh-6h4p · GitHub Advisory Database

Cite this entry

"Malware in nbmolviz-js." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 30, 2026; last updated June 30, 2026. https://supplychainattack.org/incident/malware-in-nbmolviz-js-t28o7e

Suggest a correction

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

  1. containedcritical

    Malware in autotel-mcp-instrumentation

    Malware was discovered in the npm package autotel-mcp-instrumentation. Any computer 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. containedcritical

    Malware in awaitly-libsql

    The npm package awaitly-libsql was found to contain malware. Any computer with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different system.

    npmCompromised package
  3. containedcritical

    Malware in awaitly-analyze

    The npm package awaitly-analyze was found to contain malware that grants full system compromise to attackers. Any system with this package installed should be considered fully compromised and all credentials rotated immediately from a different machine.

    npmCompromised package
  4. resolvedcritical

    Malware in awaitly

    The npm package awaitly contained malware that provided full system compromise to attackers. Any system with the package installed should be considered fully compromised and all secrets and keys rotated from a different computer.

    npmCompromised package