Malware in sol-sdk
Malware was discovered in the sol-sdk npm package. Any computer with the package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different system.
- Disclosed
- Last updated
- Blast radius
- Any system with sol-sdk installed or running; all secrets and keys on affected systems compromised
- Ecosystems
- Attack vectors
- Affected entities
- sol-sdknpm package
The sol-sdk npm package was found to contain malware. According to the GitHub advisory (GHSA-j3cf-6g4r-crmv), any system with this package installed or running should be treated as fully compromised.\n\nImmediate remediation requires rotating all secrets and keys stored on affected computers from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the compromise, given the potential for full system control to have been granted to an external entity.\n\nUsers should assume complete system compromise and take appropriate defensive measures accordingly.
Indicators of compromise
- Packages
- sol-sdk
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the sol-sdk package from all affected systems
- Assume full system compromise and conduct forensic analysis
- Monitor affected systems for signs of persistent malware or unauthorized access
- Consider rebuilding affected systems from clean media if critical infrastructure is involved
Sources
- GitHub Advisory GHSA-j3cf-6g4r-crmv · GitHub Advisory Database
Cite this entry
"Malware in sol-sdk." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-sol-sdk-yp9g64
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in autbank-core (npm)
The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.
npmCompromised package - resolvedcritical
Malicious code in adxaa (npm)
The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.
npmCompromised package - resolvedcritical
Malicious code in upload-to-gcp (npm)
upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.
npmCompromised package - resolvedcritical
Malicious code in akamai-sensor (npm)
A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.
npmCompromised packageTyposquatting