Which versions of angulaijs are malicious?

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

How do I remediate angulaijs if I installed it?

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

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

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

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

Malicious package

angulaijsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7132

Immediate action

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

npm uninstall angulaijs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

7e6dcca23f0ef3a3885ccb8fa920d5d97fe62f23c4b59af237e78c5245118153

d3ebe1ce2e0805400e58a776651bb320ee19f69acbb2f72b087bda4ddd5007d0

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for angulaijs (version 8.7.6).
If you installed it — respond
Remove angulaijs 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 angulaijs 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. angulaijs 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-04852RLUA-2026-05987

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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