Which versions of anguoarjs are malicious?

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

How do I remediate anguoarjs if I installed it?

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

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

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

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

Malicious package

anguoarjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7189

Immediate action

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

npm uninstall anguoarjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

d5d817ff1a9d27ba577b12667aec93ac35045a31e4eed1343e47dab0cf63ce54

ecf2ed3b35fb208e4c51ba56e868186dad9dd3b7df71ae328eb004008d3ee496

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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