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
- activecritical
Malware in @meme-sdk/trade
Malware discovered in the npm package @meme-sdk/trade. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malware in graphbase-js
Malware was discovered in the npm package graphbase-js. Systems with the package installed or running are considered fully compromised and require immediate remediation.
npmCompromised package - activecritical
Malware in @validator-sdk/pubkey
Malware discovered in the npm package @validator-sdk/pubkey. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malware in @validate-ethereum-address/core
The npm package @validate-ethereum-address/core was found to contain malware, potentially giving attackers full control of affected systems. Any computer with this package installed should be considered fully compromised.
npmCompromised package