Malicious Code Detected in builder-new Package - MAL-2025-16327
Summary
MAL-2025-16327: Malicious code in builder-new (npm). Affected versions are not published. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The builder-new package is an npm module designed to facilitate the building of applications by providing various utilities and tools. It is widely used in the JavaScript ecosystem for its ease of integration and functionality. However, recent findings have revealed that this package contains malicious code, posing a significant risk to users who rely on it for their development needs.
Vulnerability Detail
The vulnerability in the builder-new package stems from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall builder-newIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary workaround, users can remove the builder-new package from their project until a secure version is released. This can be done using the command: 'npm uninstall builder-new'. Consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The discovery of malicious code in the builder-new package highlights the importance of maintaining secure coding practices and regularly updating dependencies. Users are urged to take immediate action to protect their applications from potential threats.
See every vulnerability recorded for builder-new →
FAQ
The malicious code can potentially allow unauthorized access to systems, leading to data breaches or other harmful actions.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
If an immediate update is not possible, consider uninstalling the package and using alternative solutions until a secure version is available.
Regularly check the package's repository on npm or GitHub for announcements regarding updates and security patches.
Uninstalling the package should not lead to data loss, but ensure to back up your project before making significant changes.
