Which versions of angulavjs are malicious?

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

How do I remediate angulavjs if I installed it?

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

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

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

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

Malicious package

angulavjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7158

Immediate action

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

npm uninstall angulavjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

1f9114801141351d348992a836ea47628571f83b709f7cbda6b37930dc808e69

488f007c2abddea3bf38c0afd5ec6b0acf9262daf7778250ed711ba2067541bf

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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