Which versions of angulazjs are malicious?

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

How do I remediate angulazjs if I installed it?

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

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

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

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

Malicious package

angulazjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7162

Immediate action

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

npm uninstall angulazjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

78e229bf6811d2fc944b364891d6cdeb9e837d04f78fb0198aa20daaef03b7b5

34771bc0d7b79b9146be1ebccb895e4e1e1518b3f8c7d682bd4a59b1b25cf348

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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