Which versions of angufarjs are malicious?

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

How do I remediate angufarjs if I installed it?

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

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

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

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

Malicious package

angufarjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7118

Immediate action

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

npm uninstall angufarjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

3eb2df58a98b89e7e9032d5ee58baa21a90541ed12176eb82488ceca8e6fe6d9

cb8f3281e7147e3d9616b3a948e4bb303e540d6ee8aaf306b363f4f89dcab40f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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