Which versions of anguiarjs are malicious?

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

How do I remediate anguiarjs if I installed it?

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

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

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

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

Malicious package

anguiarjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7121

Immediate action

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

npm uninstall anguiarjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

066fec69ad37ee44d629e518a97fb87ee8b848aa7f1d31c5bf4d93b6e9e25d7c

867f10bc6eae3e0050ba3227049ee9676c2a699d6b82df29b05a73007c131d64

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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