Which versions of angudarjs are malicious?

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

How do I remediate angudarjs if I installed it?

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

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

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

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

Malicious package

angudarjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7116

Immediate action

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

npm uninstall angudarjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

22a4902c3cfde0451011a6e43723920a19ceb89d6e4b27e7d9abc119e67a8ad4

bb6280694ec92d4bf4eb63df1b298b065f5ac19b7b113dea0267b59320967e6e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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