Which versions of angutarjs are malicious?

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

How do I remediate angutarjs if I installed it?

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

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

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

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

Malicious package

angutarjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7193

Immediate action

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

npm uninstall angutarjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

0cd4cad0f705cfbcd3981e55d9f7a63fe16616f908d7f8d203b80cf4fc25490b

67c41a449874ff12a50344aac619bd824ab0c8f0049f623ddc759b7c5d8fa80d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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