Malware in rstreams-shard-util
Malware was discovered in the npm package rstreams-shard-util, resulting in full system compromise of any computer with the package installed or running. The advisory recommends immediate removal of the package and rotation of all secrets and keys from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- rstreams-shard-util
A critical malware incident was identified in the npm package rstreams-shard-util. According to the GitHub Security Advisory (GHSA-29q5-mm45-3xm3), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory indicates that the malware grants outside entities full control of affected systems. All secrets and keys stored on compromised computers should be rotated immediately from a different, unaffected computer.\n\nWhile removal of the package is recommended, the advisory notes that full control may have been given to an outside entity, meaning there is no guarantee that package removal will eliminate all malicious software resulting from the installation.
Indicators of compromise
- Packages
- rstreams-shard-util
Remediation
- Remove the rstreams-shard-util package from all systems
- Rotate all secrets, keys, and credentials from a different, unaffected computer
- Conduct a full security audit of any system that had the package installed
- Monitor affected systems for signs of unauthorized access or persistence mechanisms
- Review logs for any suspicious activity during the period the package was installed
Sources
- GitHub Advisory GHSA-29q5-mm45-3xm3 · GitHub Advisory Database
Cite this entry
"Malware in rstreams-shard-util." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 25, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-rstreams-shard-util-xoaffg
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