Which versions of anguparjs are malicious?

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

How do I remediate anguparjs if I installed it?

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

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

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

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

Malicious package

anguparjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7190

Immediate action

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

npm uninstall anguparjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

9395e286dd091ed7c0da4c62dc0fc98d3e7c5ad2b6a93e03be0b4b7f3ccac8d9

e5c7177f7c17211d0eaf7cfaaf2cb37a95b2c4a9f85e1aa6dd03d27922ee56c3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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