Which versions of angulaljs are malicious?

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

How do I remediate angulaljs if I installed it?

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

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

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

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

Malicious package

angulaljsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7135

Immediate action

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

npm uninstall angulaljs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

e9aeda46b6425de3d021466fe3c5ed59350f119615d687dd4c6b3caea6753b16

c6f4163151290115e2c1d57e1fa0aa1ca40ace9bc66469f5b8c3e82910e6993b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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