Which versions of angujarjs are malicious?

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

How do I remediate angujarjs if I installed it?

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

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

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

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

Malicious package

angujarjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7122

Immediate action

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

npm uninstall angujarjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

c3e5071866446311985efcf1237f49b0a7af0280a9a6f218c68d1beae6ce2bba

e19d7b55075b22f5b7351d744c595f312229859b52cbba89db8aaed809153e94

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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