Which versions of anguwarjs are malicious?

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

How do I remediate anguwarjs if I installed it?

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

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

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

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

Malicious package

anguwarjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7196

Immediate action

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

npm uninstall anguwarjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

0df733e6923e6ebee13c360f65cb00d994b16ccdb8c9afa37d1632d09df81197

7eb36a0ddd0349f4b7133a16c5cfb9e4885ed196ec148b4c967d928e22a0b807

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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