@zmtcdn/componentsnpm
Advisory published Updated
@zmtcdn/components is a confirmed malicious npm package (MAL-2026-18372) that steals credentials and exfiltrates sensitive data (malicious version 9999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @zmtcdn/components (npm)
What this malware does
@zmtcdn/[email protected] 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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for @zmtcdn/components (version 9999.0.0).
If you installed it — respond
@zmtcdn/components is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @zmtcdn/components was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- InvisiRisk, Inc. · finder
Detect & block this
O3 blocks @zmtcdn/components-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.