privacy-sdknpm
Malicious code in privacy-sdk (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
[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.
Malicious versions
Indicators of compromise (SHA-256)
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Scan your dependencies
O3 Security blocks malicious packages like this at install time and in CI.
Supply-chain protection