# MAL-2026-4571: Malicious code in get-deps-path (npm)


- **Type:** Malicious package
- **Package:** `get-deps-path` (npm)
- **Published:** 20 May 2026
- **Also known as:** GHSA-c852-72hm-gxvf

## What is MAL-2026-4571?

MAL-2026-4571 is a malicious package in get-deps-path, published on 20 May 2026. 

### Official description

On require(), get-deps-path immediately invokes getPlugin(), which performs an HTTP fetch to https://jsonkeeper.com/b/QBRMI (an anonymous public paste host where any user can mutate content) and passes the response's `model` field directly to eval(). The fetched JavaScript executes in the installer's Node process with no integrity check, no version pin, and no signature verification — whoever controls the paste controls code execution on every machine that imports this module. The package additionally masquerades: package.json keywords are ['koa','middleware','compose'] and index.js is a koa-compose clone, while the package name and README advertise unrelated 'dependency install' functionality. The mismatch between the advertised purpose, the visible source code, and the embedded import-time eval-from-mutable-URL is the cover-story shape of a deliberate backdoor, not a misconfiguration.

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

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

## Sources

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

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