Which versions of angukarjs are malicious?

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

How do I remediate angukarjs if I installed it?

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

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

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

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

Malicious package

angukarjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7123

Immediate action

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

npm uninstall angukarjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

16c50918ea7e631b01c760d3212e8faba956a511bb8371e92fc4513b5ab831f2

e72effd7c2f4352b92745dc7551c042a46f785cb10a6513b271f1cecd2df11d1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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