Which versions of angulaejs are malicious?

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

How do I remediate angulaejs if I installed it?

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

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

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

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

Malicious package

angulaejsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7128

Immediate action

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

npm uninstall angulaejs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

8c50e8fe8c4966961e9264e44bbf85224adc6b99308f40b601129d358d873566

e6a625a95c323ed4398f8b49a5b8c0ec3fd9087288e373ba4e1bc61efbcea08e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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