Which versions of angulabjs are malicious?

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

How do I remediate angulabjs if I installed it?

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

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

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

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

Malicious package

angulabjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7125

Immediate action

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

npm uninstall angulabjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

8419bfa6dff8b5fb138a51c72b3af3276c3ffdf0083808f8f7f10855430ce551

568242cc9a4e8e3cef379a6c766e3e5f1631bd7d700ae9147795abac07fb2a69

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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