Advisory

MAL-2026-6412

Also known as: GHSA-m97m-v5gv-jm47

Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.

Summary

Malicious code in nabisco (npm)

Details

---
_-= Per source details. Do not edit below this line.=-_

Source: amazon-inspector (9d0ed482ca35ed621384d6d91c398fe605352571a710d8f4222af056cedf48bb)
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.

Source: ghsa-malware (4c6b974c237c0a7f1806c58521bb7f5353e013785144f2124b21d0fe676c2b7c)
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.

Severity

Not rated by the source.

Dates

Published
2026-06-25 02:16 UTC
Modified
2026-07-23 07:52 UTC

Affected packages and fixes

nabisco

npm · All systems

Affected

  • introduced 0 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: OpenSSF Malicious Packages · Apache-2.0

Sources & licences