Which versions of angulawjs are malicious?

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

How do I remediate angulawjs if I installed it?

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

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

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

Search your lockfiles and build artifacts for angulawjs (2 malicious versions).

Malicious package

angulawjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

angulawjs is a confirmed malicious npm package (MAL-2026-7159) that executes malicious code on install (malicious versions 1.1.4, 8.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in angulawjs (npm)

MAL-2026-7159

Immediate action

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

npm uninstall angulawjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

38a3f06b4b69bf608ba8de07981dd0dc751c862eb13f61c363cf529c4d6fdb41

608cc4ff8fb4a4a9468f335a8e46f80931b0309a4879c2b88f109393d785335f

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for angulawjs (2 malicious versions).
If you installed it — respond
Remove angulawjs 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 angulawjs 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. angulawjs on npm has been identified as a malicious package (versions 1.1.4, 8.7.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04879RLUA-2026-06014

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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