Malicious Code Vulnerability in @angulaar/cli Package
Summary
MAL-2026-17536: Malicious code in @angulaar/cli (npm). Affects @angulaar/cli versions 22.2.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 @angulaar/cli package is a deceptive clone of the widely used @angular/cli package, which is essential for Angular application development. It provides command-line tools for creating, building, and managing Angular projects. However, this malicious version has been crafted to mislead developers, as it closely resembles the legitimate package but contains harmful code.
Vulnerability Detail
The vulnerability arises from the @angulaar/cli package, which is a one-character alteration of the legitimate @angular/cli package. This malicious package copies the README, LICENSE headers, and source files from the original package, making it appear trustworthy. However, it alters the dependencies to include '@modelcontextprotocol/server', a non-official package name. This allows the installation of potentially harmful code during the npm install process, posing a significant risk to developers who mistakenly use this package instead of the legitimate one.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @angulaar/cliIf 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, ensure that you are using the correct package name when installing Angular CLI. Always verify the package name before installation to avoid confusion. You can also use the following command to check for the presence of the malicious package:
npm list @angulaar/cli
Conclusion
The @angulaar/cli package poses a significant threat to developers due to its malicious nature. By understanding the risks and taking appropriate actions, such as uninstalling the malicious package and using the official version, developers can protect their projects from potential harm.
See every vulnerability recorded for @angulaar/cli →
FAQ
The @angulaar/cli package is a malicious clone of the official @angular/cli package, designed to deceive developers into installing harmful code.
You can check your package.json or use the command 'npm list @angulaar/cli' to see if the malicious package is present in your project.
You should uninstall the @angulaar/cli package immediately and install the official @angular/cli package instead.
If the malicious package is installed, it can execute harmful code on your system, potentially compromising your project and its dependencies.
Yes, Vulert can monitor your project for open-source vulnerabilities using your package-lock.json file. You can check for vulnerabilities in real-time without needing to install any software.
