Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@angulaar/clinpm

Advisory published Updated

@angulaar/cli is a confirmed malicious npm package (MAL-2026-17536) that typosquats a legitimate package to trick installs (malicious version 22.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @angulaar/cli (npm)

MAL-2026-17536
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @angulaar/cli

What this malware does

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.

Malicious versions

1 flagged
22.2.1

Indicators of compromise (SHA-256)

33d4a58c855f9b549d39f194483ee19730552bbb47a279f73237c8a403708d20

Detection & response playbook

Typosquat
  1. Find it

    Search your lockfiles and build artifacts for @angulaar/cli (version 22.2.1).

  2. If you installed it — respond

    @angulaar/cli is a typosquat — you almost certainly intended a legitimately-named package. Remove @angulaar/cli, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

  3. Did it already run?

    If @angulaar/cli was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @angulaar/cli on npm has been identified as a malicious package (version 22.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020988

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @angulaar/cli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore