Which versions of angumarjs are malicious?

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

How do I remediate angumarjs if I installed it?

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

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

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

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

Malicious package

angumarjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7187

Immediate action

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

npm uninstall angumarjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

c901d5a0e695842d9b8e3ef8331d48964aafc3f56980f70db07832916385dda8

556edd2494617435b301c0d243c5bf7f6f8c0aa48c1f40a9d6fa53cba154023b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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