Which versions of angularus are malicious?

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

How do I remediate angularus if I installed it?

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

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

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

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

Malicious package

angularusnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

angularus is a confirmed malicious npm package (MAL-2026-7153) 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 angularus (npm)

MAL-2026-7153

Immediate action

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

npm uninstall angularus

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

99bb6f9436613ed4ef40feca18e4ee4215dd30d0960ddcfb041cf0d6d527511b

a145fd4b8e48ea7caf86529c2df23e52ee4ce1454f1ff50f61edc25eea6962f6

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for angularus (version 8.7.6).
If you installed it — respond
Remove angularus 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 angularus 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. angularus 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-04873RLUA-2026-06008

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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