Which versions of angulzrjs are malicious?

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

How do I remediate angulzrjs if I installed it?

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

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

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

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

Malicious package

angulzrjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7186

Immediate action

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

npm uninstall angulzrjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

e14ebe8018a913bb80a80ffef980d9206979bf69bcd56b10eb7de5b1ef929b77

b484e5f71dd9a704d0a1b261ad1e8694c2aeddd7d7848e3c3e9f6fd2b2f7ff22

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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