Which versions of angulgrjs are malicious?

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

How do I remediate angulgrjs if I installed it?

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

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

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

Search your lockfiles and build artifacts for angulgrjs (2 malicious versions).

Malicious package

angulgrjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

angulgrjs is a confirmed malicious npm package (MAL-2026-7168) that executes malicious code on install (malicious versions 1.1.4, 8.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in angulgrjs (npm)

MAL-2026-7168

Immediate action

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

npm uninstall angulgrjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

53ccc727b53d14dc6c5a3ba9c3eab9599cd6533b25a6410cb5a95274ae529125

56629fd4e46ee0b9da9f16c75a46f81b1b78c25f8b88a60f5f8086c0fbdced0e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for angulgrjs (2 malicious versions).
If you installed it — respond
Remove angulgrjs 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 angulgrjs 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. angulgrjs on npm has been identified as a malicious package (versions 1.1.4, 8.7.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04888RLUA-2026-06023

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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