Which versions of angulaojs are malicious?

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

How do I remediate angulaojs if I installed it?

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

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

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

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

Malicious package

angulaojsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7138

Immediate action

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

npm uninstall angulaojs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

b97f4e0e7fd97050ec65004c25e38aab76e9cbad08c841ea61c5b75d2cbacc7b

60ffe712388e29434a1886f3b0a59ed6b587dbf5c68f6ef204068125f3f0e6ee

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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