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.
- 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
- 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.
Related incidents
- resolvedcritical
Malicious code in typescirpt-cli (npm)
The npm package typescirpt-cli (a typosquat of typescript-cli) contained malicious code in its postinstall script that downloads and executes a binary (main.exe) on Windows and WSL systems, and exfiltrates system metadata to a hardcoded IP address.
npmTyposquattingCompromised package - containedcritical
Malicious code in typescipt-core (npm)
The npm package typescipt-core (a typosquat of typescript) contained malicious postinstall code that downloads and executes a second-stage payload on Windows and WSL systems. The dropper exfiltrates host profile information to 193.70.34.101:20099 before fetching attacker-controlled executables.
npmCompromised packageTyposquatting - containedcritical
Malicious code in typesript-cli (npm)
The npm package 'typesript-cli' (a one-character typosquat of 'typescript') contains malicious code in its postinstall script that downloads and executes a Windows PE binary, and can cross the Linux/WSL sandbox boundary to execute payloads on the Windows host. The script also beacons to a hardcoded IP endpoint.
npmTyposquattingCompromised package - resolvedcritical
Malicious code in @mohamed_nowisar/depconf-canary-test (npm)
The npm package @mohamed_nowisar/depconf-canary-test contained malicious code in its preinstall hook that automatically collected and exfiltrated host and CI environment information to an attacker-controlled webhook endpoint without user consent.
npmCompromised package