Malware in privacy-sdk
Malware was discovered in the npm package privacy-sdk, resulting in full system compromise for any installation. The package should be removed immediately and all secrets and keys rotated from a clean system.
- Disclosed
- Last updated
- Blast radius
- Any system with privacy-sdk installed or running
- Ecosystems
- Attack vectors
- Affected entities
- privacy-sdk
A critical malware incident was identified in the npm package privacy-sdk. According to the GitHub Advisory (GHSA-wrgr-9636-hfmh), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated immediately from a different, uncompromised computer. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software that resulted from the installation.\n\nThis represents a severe supply chain attack through package distribution, affecting all users who installed the compromised version.
Indicators of compromise
- Packages
- privacy-sdk
Remediation
- Remove the privacy-sdk package immediately from all affected systems
- Rotate all secrets, keys, and credentials from a clean, uncompromised computer
- Assume full system compromise and conduct forensic analysis
- Review system logs for unauthorized access or activity during the period the package was installed
- Consider rebuilding affected systems from clean media if possible
- Notify all users and systems that may have been affected by installations of privacy-sdk
Sources
- GitHub Advisory GHSA-wrgr-9636-hfmh · GitHub Advisory Database
Cite this entry
"Malware in privacy-sdk." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 10, 2026; last updated July 10, 2026. https://supplychainattack.org/incident/malware-in-privacy-sdk-04y612
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in fetch-runtime
Malware was discovered in the npm package fetch-runtime. Any system with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package - resolvedcritical
Malicious code in ghazaly (npm)
The npm package ghazaly version 99.9.0 contained malicious code that executed a postinstall hook to collect system information (hostname, current user, IP addresses) and exfiltrate it to a Burp Collaborator domain. The package exhibited dependency-confusion characteristics with a high version number and nonsense dependencies.
npmCompromised packageDependency confusion - containedcritical
Malicious code in base65-13x (npm)
base65-13x@5.0.2 on npm contains malicious obfuscated code disguised as a legitimate base-x library. The decode() function executes a ~123KB VM-style payload with dynamic code construction and network I/O capabilities.
npmCompromised package - containedcritical
Malicious code in kit-vim-map (npm)
The npm package kit-vim-map contained malicious code that executes a remote-controlled Linux ELF binary on installation, providing the attacker with arbitrary RCE, persistence, and file exfiltration capabilities. The binary beacons to C2 server 217.60.77.63 and establishes persistence via systemd user units.
npmCompromised packageMalicious commit