# MAL-2026-18372: Malicious code in @zmtcdn/components (npm)


- **Type:** Malicious package
- **Package:** `@zmtcdn/components` (npm)
- **Published:** 28 Oct 2026

## What is MAL-2026-18372?

MAL-2026-18372 is a malicious package in @zmtcdn/components, published on 28 Oct 2026. 

### Official description

@zmtcdn/components@9999.0.0 is a dependency-confusion package with an empty `index.js` and a description of "Security research PoC". Its postinstall script runs `node postinstall.js` on npm install, which POSTs the hostname, username, platform, working directory and the names of all environment variables to `https://webhook.site/f52af355-4783-4acb-9de1-5e44b5963025`. It was published by the npm account kill_shs, which also published @zmtcdn/ui with the same script.

The package name suggests a scoped @zmtcdn component library but the version 9999.0.0 is a dependency-confusion-shaped pin. On npm install, postinstall.js runs automatically and collects os.hostname(), os.platform(), os.userInfo().username, process.cwd(), the full list of process.env key names via Object.keys(process.env), and a timestamp, then POSTs the JSON payload via https.request to the hardcoded anonymous collector https://webhook.site/f52af355-4783-4acb-9de1-5e44b5963025. Enumerating environment variable names leaks the identity of CI/secret variables present on the installer host (e.g., AWS_*, NPM_TOKEN, GITHUB_TOKEN), which is reconnaissance against the installer and typically precedes a follow-on credential-theft stage. The destination is a third-party request-logging service, not infrastructure of the apparent @zmtcdn scope.

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

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

## Sources

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

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