Which versions of anguxarjs are malicious?

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

How do I remediate anguxarjs if I installed it?

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

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

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

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

Malicious package

anguxarjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7197

Immediate action

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

npm uninstall anguxarjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

4dcb0110e66d5b5624fc0e5396cc5c312b1861bb2bfc059b7edd51fcf39ad922

c76add72de5ea131b3db9ff60dfb419f4bbe713f571e81e4ab70a38104dedbb1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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