Which versions of angulprjs are malicious?

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

How do I remediate angulprjs if I installed it?

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

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

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

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

Malicious package

angulprjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7177

Immediate action

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

npm uninstall angulprjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

e3bf56fb7ba7c7bb2ba0e084f4f4ada063116201e2d90ff360352cfb140bc42d

9c02d2eeff14e4f874ee63dbb7246499766d2fcacc492fc8d727e89727f89377

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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