Which versions of angugarjs are malicious?

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

How do I remediate angugarjs if I installed it?

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

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

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

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

Malicious package

angugarjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7119

Immediate action

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

npm uninstall angugarjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

e3766ba132ff94b761a629c86955a79277d0562359a31119829e556d3630bcd0

16b2c2240e06783fe3022e19e16aa0097e4a089f721b4c01d87c49792e4295f4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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