privacy-sdk
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-wrgr-9636-hfmh
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in privacy-sdk (npm)
---
_-= 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.
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