Which versions of angulirjs are malicious?

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

How do I remediate angulirjs if I installed it?

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

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

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

Search your lockfiles and build artifacts for angulirjs (version 8.7.6).

Malicious package

angulirjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

angulirjs is a confirmed malicious npm package (MAL-2026-7170) that executes malicious code on install (malicious version 8.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in angulirjs (npm)

MAL-2026-7170

Immediate action

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

npm uninstall angulirjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

9cc77082329ecbd22211ae245838b24fed9b03d064c1b0f3b5997d2a0e46aa5a

1d6245ffe0a6279b4923a77271b60ce28d35a6f70109ccf035d7a593eab302f5

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for angulirjs (version 8.7.6).
If you installed it — respond
Remove angulirjs 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 angulirjs 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. angulirjs on npm has been identified as a malicious package (version 8.7.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04890RLUA-2026-06025

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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