Which versions of anguvarjs are malicious?

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

How do I remediate anguvarjs if I installed it?

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

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

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

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

Malicious package

anguvarjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7195

Immediate action

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

npm uninstall anguvarjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

b6ad74d0542b1666add9484cde1032e15a1cb3d282c7c7437e3bf106aeae53f9

83fed8d5cc6438ba5b8aac05d0df44d59b7419c40f4308a1faf84c13bddbd325

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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