Which versions of nbmolviz-js are malicious?

The following npm versions of nbmolviz-js are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate nbmolviz-js if I installed it?

nbmolviz-js is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed nbmolviz-js — how do I know if it already compromised me?

If nbmolviz-js was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is nbmolviz-js part of a known attack campaign?

Yes — nbmolviz-js is associated with the GHSA-fc4r-p4fh-6h4p, IN-MAL-2026-008150 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find nbmolviz-js across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nbmolviz-js (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nbmolviz-js across your stack and pipelines.

Malicious package

nbmolviz-jsnpm

nbmolviz-js is a confirmed malicious npm package (MAL-2026-6683) that steals credentials and exfiltrates sensitive data (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nbmolviz-js (npm)

MAL-2026-6683

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall nbmolviz-js

What this malware does

No a static rule matches and no traced behavior of concern were identified in this package version. No evidence of credential access, exfiltration, install-time remote code execution, silent relay, dropper activity, or persistence mechanisms.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

01b4d35e03aa83a7f0c2707c7d2936ee8a17c7418a2bdb7c3ae700285f453e13

a233f99e766d901cd0bc65a98151969dcdbe3657a6d78f7b90ae31b958ed1045

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for nbmolviz-js (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nbmolviz-js across your stack and pipelines.
If you installed it — respond
nbmolviz-js is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If nbmolviz-js was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks nbmolviz-js before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. nbmolviz-js on npm has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-fc4r-p4fh-6h4pIN-MAL-2026-008150

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks nbmolviz-js-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database