# MAL-2026-17572: Malicious code in checkmate-remediation-assistant (npm)


- **Type:** Malicious package
- **Package:** `checkmate-remediation-assistant` (npm)
- **Published:** 5 Oct 2026

## What is MAL-2026-17572?

MAL-2026-17572 is a malicious package in checkmate-remediation-assistant, published on 5 Oct 2026. 

### Official description

checkmate-remediation-assistant@1.0.0 contains no functional code: its only behaviour is a preinstall script that runs `node index.js` on npm install. index.js collects the install directory, the user's home directory, hostname, username and DNS servers, and the full contents of /etc/passwd and /etc/hosts, then sends them as JSON in an HTTPS POST to `9q0lp9mr6ek7nrnklhzkmbpuglmda4yt.oastify.com`, a Burp Collaborator endpoint. The npm account testneo7755 published it on 2026-10-05 and it was unpublished about two minutes later; the same account published with-cte the same day with the same index.js and a different Collaborator subdomain.

The package's package.json declares a preinstall hook that runs index.js on npm install. index.js collects os.hostname(), os.userInfo(), the home directory, DNS server configuration, __dirname, the local package.json, and the contents of /etc/passwd and /etc/hosts, then transmits the collected data over HTTPS to a hardcoded Burp Collaborator (oastify.com) subdomain (9q0lp9mr6ek7nrnklhzkmbpuglmda4yt.oastify.com). The destination is an out-of-band interaction server not associated with any declared publisher or documented package purpose, and the exfiltration fires automatically on default install without user interaction.

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

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

## Sources

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

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