Which versions of angulayjs are malicious?

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

How do I remediate angulayjs if I installed it?

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

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

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

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

Malicious package

angulayjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7161

Immediate action

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

npm uninstall angulayjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

d7ea88f802597669d76bde6d009545c7a86610d37d0284268263be740367d53e

1b1751e3b3d4175ad5b85c450bab87b4ef5c2a731b55620b8f8d0191e51251ba

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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