Which versions of angulmrjs are malicious?

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

How do I remediate angulmrjs if I installed it?

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

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

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

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

Malicious package

angulmrjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7174

Immediate action

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

npm uninstall angulmrjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

46031bcb77736ebaecba4c630a8a8f2a616807dabb087ea54bdf65f5ea30f0c8

d2b7955b948dde2933fc2cfa0f8788803505de01766701ff1975af3b778fd025

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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