Which versions of angulrrjs are malicious?

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

How do I remediate angulrrjs if I installed it?

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

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

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

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

Malicious package

angulrrjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7178

Immediate action

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

npm uninstall angulrrjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

4c4ce76768e1a43aa03a923fd04fbaf07fc748fa14e3412d75e4170a959c58b7

429de5ebe663ba1c725398a7b221b72b06d1d47b6b6adaec00b492794c4a35e7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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