Malware in @shoobx/types
Malware was discovered in the npm package @shoobx/types. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @shoobx/types
A critical malware incident was identified in the npm package @shoobx/types. According to the GitHub Security Advisory (GHSA-9jhq-mjgj-698m), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory indicates that the malicious package may have granted full control of affected systems to an outside entity. All secrets and cryptographic keys stored on compromised computers should be rotated immediately from a different, unaffected system.\n\nWhile 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 initial compromise. A comprehensive security review and potential system rebuild may be necessary for affected users.
Indicators of compromise
- Packages
- @shoobx/types
Remediation
- Immediately remove @shoobx/types from all systems
- Rotate all secrets, API keys, and cryptographic credentials from a clean, unaffected computer
- Conduct a full security audit of any system that had this package installed
- Consider rebuilding affected systems from clean media if full compromise is suspected
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Monitor for any unauthorized activity on accounts or services that may have been accessed from compromised systems
Sources
- GitHub Advisory GHSA-9jhq-mjgj-698m · GitHub Advisory Database
Cite this entry
"Malware in @shoobx/types." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-shoobx-types-16vlyr
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