Which versions of angunarjs are malicious?

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

How do I remediate angunarjs if I installed it?

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

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

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

Search your lockfiles and build artifacts for angunarjs (version 1.1.4).

Malicious package

angunarjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

angunarjs is a confirmed malicious npm package (MAL-2026-7188) that executes malicious code on install (malicious version 1.1.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in angunarjs (npm)

MAL-2026-7188

Immediate action

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

npm uninstall angunarjs

Malicious versions

1 flagged

1.1.4

Indicators of compromise (SHA-256)

eeb94d7bc46efdffa3d16cf7a0410e7377a2bfb339dfa99a1abf2053f6860788

8e0baa8db7841b5b451f5814a0086c3d34cfa85d5ad1bdafd6f2f7a65e655715

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for angunarjs (version 1.1.4).
If you installed it — respond
Remove angunarjs 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 angunarjs 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. angunarjs on npm has been identified as a malicious package (version 1.1.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04908RLUA-2026-06043

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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