Malware in react-svg-render
Malware discovered in the npm package react-svg-render. 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
- react-svg-render
The npm package react-svg-render has been identified as containing malware. According to the GitHub Advisory (GHSA-h2hr-f82c-f7h5), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated from a different, uncompromised system. The package should be removed, though full removal of all malicious software cannot be guaranteed given the potential for complete system compromise.\n\nThis represents a critical supply chain attack through a compromised package in the npm ecosystem, with potential impact to all systems that have installed or executed this dependency.
Indicators of compromise
- Packages
- react-svg-render
Remediation
- Immediately isolate any system with react-svg-render installed from the network
- Rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the react-svg-render package from all systems
- Perform a full security audit and malware scan on affected systems
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if compromise is suspected
- Audit all systems that may have been accessed from compromised machines
Sources
- GitHub Advisory GHSA-h2hr-f82c-f7h5 · GitHub Advisory Database
Cite this entry
"Malware in react-svg-render." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-react-svg-render-9qpc3a
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in 3-buildsight-web (npm)
The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.
npmCompromised package - resolvedcritical
Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)
Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.
npmDependency confusionCompromised package - resolvedcritical
Malicious code in create-coin (npm)
create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.
npmCompromised packageTyposquatting - resolvedcritical
Malicious code in @syncraft-labs/vue (npm)
The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.
npmCompromised package