Malware in @gm-rvg/root-config
Malware was discovered in the npm package @gm-rvg/root-config. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @gm-rvg/root-config
A malicious package named @gm-rvg/root-config was published to npm and contains malware. Any computer that has installed or executed this package should be considered fully compromised.\n\nImmediate remediation requires rotating all secrets and keys stored on affected systems from a different, uncompromised computer. 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 initial compromise, given the potential for full system control to have been granted to an outside entity.\n\nThe advisory was published on 2026-06-29 via GitHub Security Advisory GHSA-9crf-2vxq-9j4r.
Indicators of compromise
- Packages
- @gm-rvg/root-config
Remediation
- Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
- Remove the @gm-rvg/root-config package from all affected systems
- Perform a full security audit and malware scan of any system that had this package installed
- Review system logs and access logs for any unauthorized activity during the period the package was installed
- Consider the affected system(s) potentially compromised and plan for full rebuild if critical infrastructure
Sources
- GitHub Advisory GHSA-9crf-2vxq-9j4r · GitHub Advisory Database
Cite this entry
"Malware in @gm-rvg/root-config." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-gm-rvg-root-config-h879uf
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