Which versions of anguharjs are malicious?

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

How do I remediate anguharjs if I installed it?

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

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

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

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

Malicious package

anguharjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7120

Immediate action

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

npm uninstall anguharjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

07314f4d4ec982ff7fab96614499636f7037e73d7835c4e25dc7612e80c62df0

dbae345c395b89a05836e64e7a25cabd298d279729447aaaf7c36a0dae2998c8

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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