Which versions of angularrs are malicious?

The following npm versions of angularrs are flagged malicious: 8.7.6. Treat any of these as compromised.

How do I remediate angularrs if I installed it?

Remove angularrs 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 angularrs — how do I know if it already compromised me?

If angularrs 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 angularrs part of a known attack campaign?

Yes — angularrs is associated with the RLMA-2026-04871, RLUA-2026-06006 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 angularrs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for angularrs (version 8.7.6).

Malicious package

angularrsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

angularrs is a confirmed malicious npm package (MAL-2026-7151) that executes malicious code on install (malicious version 8.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in angularrs (npm)

MAL-2026-7151

Immediate action

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

npm uninstall angularrs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

325a0577f3910ad59e87b8f3ff0a10de10c5b8f5dd12e2f1488ebafcb8492b34

e8147b4ac30bb33a6a28f62ec689a987dd036473d0e49c8f55080009208177e0

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for angularrs (version 8.7.6).
If you installed it — respond
Remove angularrs 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 angularrs 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. angularrs on npm has been identified as a malicious package (version 8.7.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04871RLUA-2026-06006

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks angularrs-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