Malware in react-resource-router-next
Malware was discovered in the npm package react-resource-router-next. The package grants full control of affected systems to an outside entity, requiring immediate removal and credential rotation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- react-resource-router-next
A malicious package named react-resource-router-next was published to npm and contains malware that compromises any system where it is installed or executed.\n\nAccording to the GitHub Advisory (GHSA-7hgr-34h5-w2m5), any computer running this package should be considered fully compromised. The advisory recommends immediate action: all secrets and keys stored on affected systems should be rotated from a different, uncompromised computer.\n\nWhile the package should be removed, the advisory notes that because the malware may grant full control of the system to an external actor, there is no guarantee that package removal alone will eliminate all malicious software that may have been installed as a result.\n\nUsers should treat any system that has had this package installed as potentially compromised and take appropriate incident response measures.
Indicators of compromise
- Packages
- react-resource-router-next
Remediation
- Immediately remove the react-resource-router-next package from all systems
- Rotate all secrets, API keys, credentials, and tokens from a different, uncompromised computer
- Perform a full security audit and malware scan of any system that had the package installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider the affected system(s) as potentially fully compromised and plan for reimaging if critical infrastructure
- Monitor for any unauthorized access attempts using rotated credentials
Sources
- GitHub Advisory GHSA-7hgr-34h5-w2m5 · GitHub Advisory Database
Cite this entry
"Malware in react-resource-router-next." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-react-resource-router-next-1qayov
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