Malware in @ravespaceio/rave-engine
Malware discovered in the npm package @ravespaceio/rave-engine. 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
- @ravespaceio/rave-engine
A malware-laden version of the npm package @ravespaceio/rave-engine has been identified and published to the npm registry. The package grants full control of affected systems to an outside entity.\n\nAny computer with this package installed or running should be considered fully compromised. All secrets, keys, and credentials stored on affected systems must be rotated immediately from a different, unaffected computer.\n\nWhile the malicious package should be removed, complete remediation cannot be guaranteed due to the level of system compromise. Additional forensic investigation and system hardening may be necessary to ensure all malicious artifacts are eliminated.\n\nThe incident was disclosed via GitHub Advisory GHSA-72c8-h2pr-vwjg on 2026-06-23.
Indicators of compromise
- Packages
- @ravespaceio/rave-engine
Remediation
- Immediately remove @ravespaceio/rave-engine from all systems
- Rotate all secrets, keys, and credentials from a clean, unaffected computer
- Perform forensic analysis on affected systems to identify additional compromise indicators
- Consider full system rebuild or replacement if compromise is confirmed
- Audit logs and network traffic for signs of data exfiltration or lateral movement
- Monitor affected systems for persistence mechanisms and unauthorized access
Sources
- GitHub Advisory GHSA-72c8-h2pr-vwjg · GitHub Advisory Database
Cite this entry
"Malware in @ravespaceio/rave-engine." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 23, 2026; last updated June 23, 2026. https://supplychainattack.org/incident/malware-in-ravespaceio-rave-engine-1amaod
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