# MAL-2026-6412: Malicious code in nabisco (npm)


- **Type:** Malicious package
- **Package:** `nabisco` (npm)
- **Published:** 25 Jun 2026
- **Also known as:** GHSA-m97m-v5gv-jm47

## What is MAL-2026-6412?

MAL-2026-6412 is a malicious package in nabisco, published on 25 Jun 2026. 

### Official description

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.

## What should I do about MAL-2026-6412?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-6412 is a malicious package: nabisco (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-6412/ (Markdown: https://insights.sbomify.com/MAL-2026-6412/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-6412

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-6412/
Summaries are generated and may contain mistakes; the official description above is the record.