Which versions of angulnrjs are malicious?

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

How do I remediate angulnrjs if I installed it?

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

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

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

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

Malicious package

angulnrjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7175

Immediate action

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

npm uninstall angulnrjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

e4ec8a9c8cccd972079b94a84725739f10795b07a92c2bc6e8ed5ac53391781d

2cc7067c76094ddf85330aeff2d8b72315b960a98ea696f1fae6663fe1f6039f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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