Which versions of angylarjs are malicious?

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

How do I remediate angylarjs if I installed it?

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

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

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

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

Malicious package

angylarjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7203

Immediate action

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

npm uninstall angylarjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

979999f25e6941c0fb3b7c2691e01dfafa131173cf7d39bc1df9a8ccef134357

d771aca2c547a3b1ff53ad5da179c33e8d6e934a6289e3ca7f014d28d7c941bc

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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