Malicious Code Detected in @angular_devkit/build-webpack: Version 99.1.1 Compromised
Summary
MAL-2025-6870: Malicious code in @angular_devkit/build-webpack (npm). Affects @angular_devkit/build-webpack versions 99.1.1. 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 @angular_devkit/build-webpack package is a crucial tool in the Angular ecosystem, providing developers with the ability to build and bundle Angular applications efficiently. It is widely used for its robust features that streamline the development process. However, version 99.1.1 has been identified as containing malicious code that poses significant security risks to users.
Vulnerability Detail
The vulnerability originates from the malicious version 99.1.1 of the @angular_devkit/build-webpack package. It has been flagged for communicating with a domain associated with malicious activities and executing commands that can compromise the security of the host system. This could lead to unauthorized access, data breaches, or further exploitation of the affected system.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @angular_devkit/build-webpackIf 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
If immediate updating is not feasible, consider removing the package temporarily from your project until a secure version is available. You can do this by executing 'npm uninstall @angular_devkit/build-webpack'.
Conclusion
The identification of malicious code in the @angular_devkit/build-webpack package version 99.1.1 highlights the importance of maintaining secure dependencies in software development. Users are advised to update to a secure version promptly and utilize tools like Vulert for continuous monitoring of vulnerabilities.
See every vulnerability recorded for @angular_devkit/build-webpack →
FAQ
Using the compromised version can lead to security vulnerabilities, including unauthorized access to your system and potential data breaches.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By simply uploading your package-lock.json file, you can check for vulnerabilities without needing to install any software.
Yes, Vulert provides real-time monitoring for open-source vulnerabilities. You can access the Vulert playground at Vulert Scanner to check your application without any signup.
If you cannot update the package right away, consider removing it from your project until a secure version is released to mitigate risks.
Regularly check for updates from the package maintainers and utilize tools like Vulert for ongoing monitoring of your dependencies.
