Malicious code in privacy-sdk (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-5451
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5c92b5d6dae289f8667ca24f2a941473b65e560f6937874f68ff26ed24d58969) [email protected] is a hollow wrapper (index.js is `module.exports = {}`, blank description, blank author) whose sole runtime dependency is declared as a raw tarball URL: `"ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.8.9.tgz"`. On `npm install privacy-sdk`, npm fetches that tarball directly from the GCS bucket — bypassing the npm registry's publication, audit, and integrity-hash mechanisms — and installs it, executing any lifecycle scripts (preinstall/install/postinstall) bundled inside. The bucket and `depenconf` path do not correspond to any identifiable publisher, the URL has no integrity field, and the bytes at that URL are mutable by whoever controls the bucket. The version `99.9.1` is the canonical high-version dependency-confusion pattern used to outrank an organization's internal `privacy-sdk` package, and the generic name compounds that risk. The package has no advertised functionality of its own; its only effect on install is to deliver attacker-controlled code into the installer's environment via the smuggled tarball. ## Source: ghsa-malware (1825b4f06e2197776dc61ab1ddea99c0afeeae873e0d1a9c010c90d1483defea) 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:25:01 UTC
- Source modified
- 1 Sep 2026 11:31:12 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.