Which versions of angucarjs are malicious?

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

How do I remediate angucarjs if I installed it?

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

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

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

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

Malicious package

angucarjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7115

Immediate action

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

npm uninstall angucarjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

57bacd98122a57bfa6fd05b9f5bf1eb05f743aca6f14bf2c04a59916712251fd

f2f01c59dafefef6f9d89c3d37cd6615ab708db708fb227c80bf3859e217c885

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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