Which versions of angulapjs are malicious?

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

How do I remediate angulapjs if I installed it?

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

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

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

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

Malicious package

angulapjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7139

Immediate action

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

npm uninstall angulapjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

8b7b77b3118e1e447099e02b49e2c947f3d920f27e0484efe8000ed698cfc23b

600b0a57519efca936a72cfc3ba9a4ba3d9aba0accfef09c268c49746204d8f5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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