@angulaar/cli
Affected
- Versions:
22.2.1
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in @angulaar/cli (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (33d4a58c855f9b549d39f194483ee19730552bbb47a279f73237c8a403708d20)
Package name '@angulaar/cli' (double 'a') is a one-character edit of '@angular/cli'; README, LICENSE headers, and source files are copied verbatim from the real Angular CLI (Google LLC copyright, angular.dev license URLs, README pointing issues to github.com/angular/angular-cli). The manifest's dependencies list has been altered from the upstream package: real @angular/cli depends on '@modelcontextprotocol/sdk', while this package declares '@modelcontextprotocol/server': '2.0.0' and requires it from src/commands/mcp/cli.js and mcp-server.js. '@modelcontextprotocol/server' is not the official MCP package name, so npm install resolves and installs whatever bytes are published under that attacker-chosen name/version, executing any lifecycle scripts in that dependency on the installer's host and loading its code in-process on later ng mcp invocations. The lookalike package name, cloned source, and swapped MCP dependency together form a dependency-confusion delivery vector against developers who mistype the real @angular/cli name.
Not rated by the source.
22.2.1None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0