Malicious code in commons-ui-styles (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-5437
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (8b9fb701d18bde61d1dc783f0575a4d83bc0eba2653bd0832d0fc26bc9e85b48) [email protected] is an empty placeholder package (index.js exports `{}`, description/author blank, version bumped to 99.9.1 — the classic dependency-confusion override shape) whose only on-install effect is dependency resolution. Its package.json declares a transitive dependency `ltidisafe` resolved from a hardcoded non-registry tarball URL (`https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.9.6.tgz`) on a Google Cloud Storage bucket. The path segment literally contains `depenconf`, indicating dependency-confusion tooling. On `npm install commons-ui-styles`, npm fetches whatever bytes that bucket currently serves and installs them as a dependency; any preinstall/install/postinstall lifecycle scripts in the fetched tarball run on the installer's host. The bucket owner controls the payload contents at any time, with no version pinning to the npm registry, no integrity check beyond what npm computes against the live download, and no relationship to a documented publisher. ## Source: ghsa-malware (0e1b59b1a66b5b52881d2f9babca5a402325f4454444f4e318670406c17ae780) 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.
- Source published
- 9 Jun 2026 17:24:18 UTC
- Source modified
- 1 Sep 2026 11:31:31 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.