ux-metrics-client-interaction-subscribernpm
ux-metrics-client-interaction-subscriber is a confirmed malicious npm package (MAL-2026-15545) that executes malicious code on install (malicious version 45.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in ux-metrics-client-interaction-subscriber (npm)
What this malware does
package.json line 11 declares a dependency whose key equals the package's own name (ux-metrics-client-interaction-subscriber) and whose value is a bare HTTPS URL to a non-registry host: https://repo.securityctrl.com/ux-metrics-client-interaction-subscriber. On npm install, npm fetches whatever tarball that URL returns and installs it, running any lifecycle scripts contained in it, with no version pin, no integrity hash, and no signature check. The shipped index.js is an inert stub, so the manifest itself is the entire delivery mechanism: control of repo.securityctrl.com equals code execution on the installer's machine. The self-name dependency-confusion shape (dependency key equals the package's own name, implausibly high version 45.0.0) is consistent with an attempt to win resolution against an internal package of the same name.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ux-metrics-client-interaction-subscriber (version 45.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ux-metrics-client-interaction-subscriber across your stack and pipelines.
If you installed it — respond
Remove ux-metrics-client-interaction-subscriber from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If ux-metrics-client-interaction-subscriber was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks ux-metrics-client-interaction-subscriber before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks ux-metrics-client-interaction-subscriber-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.