Which versions of angulajjs are malicious?

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

How do I remediate angulajjs if I installed it?

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

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

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

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

Malicious package

angulajjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7133

Immediate action

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

npm uninstall angulajjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

11d8dcb8804384aa449a6f7551193338356074f6f7a7b5814fe0e7c7ae59271f

82f9439007109e46cb5980d7942efdffc710cccbe1eb21aa0dc8b11b6b033662

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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