Which versions of angulyrjs are malicious?

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

How do I remediate angulyrjs if I installed it?

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

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

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

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

Malicious package

angulyrjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7185

Immediate action

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

npm uninstall angulyrjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

822d3cedca686e3d6f28bb943e2bdf31b29b0bdb2307d18927d12e182adee627

ede139189bc1014f9e7c1e5e7c2b5cad25485561d0931c78aab0a09233d407bd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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