metrics-uinpm
metrics-ui is a confirmed malicious npm package (MAL-2026-11473) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in metrics-ui (npm)
What this malware does
metrics-ui is a functionally empty npm package (hollow index.js, no scripts) whose only effect on installers is pulling in a runtime dependency resolved from a hardcoded off-registry URL. package.json declares dependencies.ltidisafe = "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.4.4.tgz", causing npm to fetch and install that tarball's contents into node_modules on every npm install metrics-ui. The tarball is served from a Google Cloud Storage bucket path controlled by whoever owns the bucket, bypassing npm registry publication, scanning, and immutability guarantees; the bucket contents can be swapped at any time and any lifecycle hooks or top-level require() side effects in the fetched package then run in the installer's environment. The package name resembles common analytics/UI naming while shipping no actual UI or metrics code, consistent with a dropper-lure shape whose sole purpose is to force-resolve attacker-controlled code into consumers' dependency graphs.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
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 metrics-ui (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging metrics-ui across your stack and pipelines.
If you installed it — respond
Remove metrics-ui 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 metrics-ui 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 metrics-ui 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 metrics-ui-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.