Which versions of angulsrjs are malicious?

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

How do I remediate angulsrjs if I installed it?

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

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

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

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

Malicious package

angulsrjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7179

Immediate action

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

npm uninstall angulsrjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

ddfebfd8aeded791f40dc54ee630064401c5a1d8c5337c6dd4c1b2da82b4e04c

ba783a5e1016f69b18ee0890c39106686de5086febd66bd9bcebec09b3a50c48

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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