Which versions of angulaajs are malicious?

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

How do I remediate angulaajs if I installed it?

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

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

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

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

Malicious package

angulaajsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7124

Immediate action

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

npm uninstall angulaajs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

59f35d0c106b4eb464f26646a10254b90a7dc746cfdb8c4580d36ec372c0ea19

92de8f136613aa8106e732a314ef3bafd340e80994c0498a98de61985c4f2844

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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