Which versions of angulaujs are malicious?

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

How do I remediate angulaujs if I installed it?

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

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

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

Search your lockfiles and build artifacts for angulaujs (2 malicious versions).

Malicious package

angulaujsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

angulaujs is a confirmed malicious npm package (MAL-2026-7157) that executes malicious code on install (malicious versions 1.1.4, 8.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in angulaujs (npm)

MAL-2026-7157

Immediate action

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

npm uninstall angulaujs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

961a6fac72f59d08bd4d8f76d5989896f27900b8b822f87a7b9c7f3453fe742c

504142027a4c388e3d92c98e64287227aa2e831c340d4c940311fb2640ec95e1

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for angulaujs (2 malicious versions).
If you installed it — respond
Remove angulaujs 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 angulaujs 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. angulaujs on npm has been identified as a malicious package (versions 1.1.4, 8.7.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04877RLUA-2026-06012

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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