Which versions of angzlarjs are malicious?

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

How do I remediate angzlarjs if I installed it?

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

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

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

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

Malicious package

angzlarjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7204

Immediate action

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

npm uninstall angzlarjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

7890ff3eba9c0963b9de03a6de11a7c7fb6ff1d0bed9e4faac291044765c1df0

f21ec587978d3741478c742497e45514d2cf5749df7401020b15de0390d2ff21

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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