@zmtcdn/uinpm
Advisory published Updated
@zmtcdn/ui is a confirmed malicious npm package (MAL-2026-18373) that steals credentials and exfiltrates sensitive data (malicious versions 9999.0.0, 9999.0.7). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @zmtcdn/ui (npm)
What this malware does
@zmtcdn/ui 9999.0.0 and 9999.0.7 are dependency-confusion packages with an empty index.js and a description of "Security research PoC". Their 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://www.hinny.shop/api. They were published by the npm account kill_shs, which also published @zmtcdn/components with the same script.
The postinstall.js lifecycle script runs automatically on npm install and collects installer-identifying data — os.hostname(), os.platform(), os.userInfo().username, process.cwd(), the list of process.env key names, and a timestamp — then POSTs the JSON blob via https.request to the hardcoded endpoint https://www.hinny.shop/api. The package name uses a vendor-style scope (@zmtcdn/ui) and an implausibly high version (9999.0.7) consistent with a dependency-confusion lure, and the fetch destination is unrelated to any declared publisher. No user opt-in, no documentation of the beacon, and no legitimate functional purpose for sending this data off-host at install time.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for @zmtcdn/ui (2 malicious versions).
If you installed it — respond
@zmtcdn/ui 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/ui 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/ui-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.