Which versions of anguearjs are malicious?

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

How do I remediate anguearjs if I installed it?

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

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

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

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

Malicious package

anguearjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7117

Immediate action

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

npm uninstall anguearjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

b901e42de8a8d328aeb08c7382b63632826744c55c086b9ed31559e0d5146cb6

f3ab96e69aa3d5e09893c3b19b22c50c00233ba3a5751c4c1973de660a381e78

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for anguearjs (2 malicious versions).
If you installed it — respond
Remove anguearjs 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 anguearjs 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. anguearjs 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-04837RLUA-2026-05972

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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