# MAL-2026-2930: Malicious code in path-internal (npm)


- **Type:** Malicious package
- **Package:** `path-internal` (npm)
- **Published:** 14 Apr 2026
- **Also known as:** GHSA-55cg-pqmh-hh6w

## What is MAL-2026-2930?

MAL-2026-2930 is a malicious package in path-internal, published on 14 Apr 2026. 

### Official description

The package presents itself as a copy of the Node.js core `path` module (name `path-internal`, README: "exact copy of the NodeJS 'path' module") and ships the upstream Joyent path implementation with a malicious dropper spliced between `posix.basename` and `posix.extname` in `path.js`. On `require('path-internal')`, the module decodes a base64-encoded URL (`https://www.jsonkeeper.com/b/YCW2F`, stored under the misleading variable name `randomStringRe`), fetches the JSON document at that URL, and passes `data.content` straight to `eval()`. A second identical IIFE for `https://www.jsonkeeper.com/b/TPQHE` is present (commented out) under `tokenStringRe`. jsonkeeper.com is an anonymous, mutable paste host: the attacker can change the served payload at any time to execute arbitrary code in-process on every installer that imports the package. The base64 obfuscation, the regex-shaped decoy variable names, the splice into a verbatim copy of a Node stdlib module, and the typosquat name (with the README also confusingly suggesting `npm install --save path-external`) collectively confirm malicious intent rather than negligence.

The OpenSSF Package Analysis project identified 'path-internal' @ 1.0.10 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

- The package executes one or more commands associated with malicious behavior.

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

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

## Sources

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

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