Which versions of angularvs are malicious?

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

How do I remediate angularvs if I installed it?

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

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

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

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

Malicious package

angularvsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7154

Immediate action

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

npm uninstall angularvs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

0694df64b3d9a955d78e30e99a0447cf967bf0d30f6582387ed0af0f1f644e45

c9f6c989175231a8a1c27d4a6d8e3191a5b26d11add791e90b17db2f70d2de2b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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