Which versions of angulasjs are malicious?

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

How do I remediate angulasjs if I installed it?

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

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

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

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

Malicious package

angulasjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7155

Immediate action

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

npm uninstall angulasjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

1469d87133976d97bad00339145fe4c2ee92878f9300a0f97ebce5ee3b72c12a

d9df66bd8bdc4f6f580469570f84084d3508e09fa1d1509f783f230b3d6870d9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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