Which versions of angulerjs are malicious?

The following npm versions of angulerjs are flagged malicious: 1.1.1, 1.1.2, 1.1.3, 1.1.4, 8.7.6. Treat any of these as compromised.

How do I remediate angulerjs if I installed it?

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

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

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

Search your lockfiles and build artifacts for angulerjs (5 malicious versions).

Malicious package

angulerjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

angulerjs is a confirmed malicious npm package (MAL-2026-7166) that executes malicious code on install (malicious versions 1.1.1, 1.1.2, 1.1.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in angulerjs (npm)

MAL-2026-7166

Immediate action

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

npm uninstall angulerjs

Malicious versions

5 flagged

1.1.11.1.21.1.31.1.48.7.6

Indicators of compromise (SHA-256)

04448e61b0cdac74e528800132a995ee285eda7862218c8c6a5295f9c0d3c5ea

9ab6b5295c61a2446dfa3b73d0194e18ffb224b52e254dccb3424a9ca9092d51

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for angulerjs (5 malicious versions).
If you installed it — respond
Remove angulerjs 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 angulerjs 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. angulerjs on npm has been identified as a malicious package (versions 1.1.1, 1.1.2, 1.1.3, 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-04886RLUA-2026-06021

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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