Which versions of angulorjs are malicious?

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

How do I remediate angulorjs if I installed it?

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

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

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

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

Malicious package

angulorjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7176

Immediate action

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

npm uninstall angulorjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

9343614423b8b927273e52327687e209e559619f04679202e11b8f0c16f4345f

e765969de6e38f4f99d95b0059b313facabe06d7ba517fbeeba6a5bc294120b3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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