Which versions of angulanjs are malicious?

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

How do I remediate angulanjs if I installed it?

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

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

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

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

Malicious package

angulanjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7137

Immediate action

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

npm uninstall angulanjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

adad2b696c1f5cbc6a73ba15315088a99f787603ca0f67fbbea246f3c4fdfaee

104a6ad50fdc5ede5b5146604ef74f1f3fe97ca97ad737fd48a9c17eed69a141

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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