Which versions of angulatjs are malicious?

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

How do I remediate angulatjs if I installed it?

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

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

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

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

Malicious package

angulatjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7156

Immediate action

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

npm uninstall angulatjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

95ac454ac470150961da9bbd048f3b46c567dedfda8295540aaaa9fc56ab14f4

3d0f6c3d801dca2a38e37679e9e1e6060ffc3a6cf45e74055f85bba233569488

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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