Which versions of angulacjs are malicious?

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

How do I remediate angulacjs if I installed it?

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

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

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

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

Malicious package

angulacjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7126

Immediate action

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

npm uninstall angulacjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

0ec3038ccf39cbc38fa0b1b08fa68bec832b25471e3f3b8dca26886a53b62d4e

6d9167e082f8579a4a18565ce9c099758119343670a7dc21b504322d385bcacf

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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