Which versions of angxlarjs are malicious?

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

How do I remediate angxlarjs if I installed it?

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

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

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

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

Malicious package

angxlarjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7202

Immediate action

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

npm uninstall angxlarjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

84c70b4309127f88829c012436fe010404b48e6b29ef2303fc1d981c7aa91663

bb0f1428e1a344b06f4f3af645e66922eaf263283f473bf55e4f35dde9609a8d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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