Which versions of nabisco are malicious?

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

How do I remediate nabisco if I installed it?

nabisco 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 nabisco — how do I know if it already compromised me?

If nabisco 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 nabisco part of a known attack campaign?

Yes — nabisco is associated with the GHSA-m97m-v5gv-jm47, IN-MAL-2026-008156, RLMA-2026-05578 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 nabisco 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 nabisco (version 0.0.1-poc). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nabisco across your stack and pipelines.

Malicious package

nabisconpm

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

Malicious code in nabisco (npm)

MAL-2026-6412

Immediate action

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

npm uninstall nabisco

What this malware does

Package self-describes as a security PoC for dependency confusion targeting an internal HubSpot module name. On install, postinstall.js prints a confirmation line ('nabisco resolved from registry.npmjs.org and executed') along with the host's name (os.hostname()) and a timestamp to stdout. No network egress, credential access, filesystem persistence, or remote payload fetch is present in the current version — the postinstall is purely a local log statement. The harm shape is the namespace squat itself: any HubSpot build that misroutes a request for the internal 'nabisco' module to the public registry will execute this package's code at install time, and any future republish under the same name could add a real payload while keeping the same install path. Routing to human review for a takedown / dispute decision rather than blocking on confirmed installer-side harm.

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-poc

Indicators of compromise (SHA-256)

4c6b974c237c0a7f1806c58521bb7f5353e013785144f2124b21d0fe676c2b7c

9d0ed482ca35ed621384d6d91c398fe605352571a710d8f4222af056cedf48bb

dd7e36be55c5bc0d6ff12d5b7664445ca5bcdee7ad0f3050ad302ddbbf0bcd85

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 nabisco (version 0.0.1-poc). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nabisco across your stack and pipelines.
If you installed it — respond
nabisco 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 nabisco 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 nabisco 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. nabisco on npm has been identified as a malicious package (version 0.0.1-poc flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-m97m-v5gv-jm47IN-MAL-2026-008156RLMA-2026-05578

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks nabisco-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