Malware in @builder.io/dev-tools
Malware was discovered in the npm package @builder.io/dev-tools, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @builder.io/dev-tools
A critical malware incident was identified in the npm package @builder.io/dev-tools. According to the GitHub Advisory (GHSA-4fm3-j964-p869), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory indicates that all secrets and keys stored on affected computers should be rotated immediately from a different, uncompromised system. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning there is no guarantee that removing the package alone will eliminate all malicious software resulting from the installation.\n\nThis represents a critical supply chain attack through a compromised npm package with potential for widespread impact across development environments and systems using the affected package.
Indicators of compromise
- Packages
- @builder.io/dev-tools
Remediation
- Immediately remove @builder.io/dev-tools from all systems
- Rotate all secrets, API keys, credentials, and authentication 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) potentially compromised and plan for full rebuild if critical infrastructure
- Monitor for any unauthorized access to rotated credentials
Sources
- GitHub Advisory GHSA-4fm3-j964-p869 · GitHub Advisory Database
Cite this entry
"Malware in @builder.io/dev-tools." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 10, 2026; last updated June 10, 2026. https://supplychainattack.org/incident/malware-in-builder-io-dev-tools-vyxvq5
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 -john-wick-4-keanu-reeves-peliculas-completa-varindo-h-d-varindo-en-casa-lliena- (npm)
Malicious code was published in an npm package with a deceptive name referencing a movie title. The package was identified and documented by the OpenSSF malicious packages project.
npmCompromised package - resolvedcritical
Malicious code in -john-wick-keanu-reeves-pelicula-completa-4-k-varindo-en-casa-en-lienia-lliena-love (npm)
A malicious npm package with a deceptive name containing movie-related keywords was published to the npm registry. The package contained malicious code and was identified by the OpenSSF malicious packages project.
npmCompromised package - resolvedcritical
Malicious code in -john-wick-keanu-reeves-pelicula-completa-4-k-varindo-en-casa-en-lienia-lliena- (npm)
Malicious code was published in an npm package with a deceptive name referencing a movie title. The package was identified and cataloged by the OpenSSF malicious packages database.
npmCompromised package - containedcritical
Malicious code in -pem-misa (npm)
The npm package -pem-misa contains malicious code designed to automatically generate and republish derivative packages with randomized names to the npm registry. The attack is part of a broader tea.xyz token reward campaign that flooded npm with similar malicious packages.
npmCompromised packageMalicious commit