Which versions of angulamjs are malicious?

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

How do I remediate angulamjs if I installed it?

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

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

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

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

Malicious package

angulamjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7136

Immediate action

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

npm uninstall angulamjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

3d606926f71e6c861354d5e386a11dcab0b15bb2f11ca126ee139f1dc438d445

a29c2746123d34c67281488d094c03bb4b7c5a23d2ed1bfa94a14e32f19879eb

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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