Which versions of angulcrjs are malicious?

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

How do I remediate angulcrjs if I installed it?

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

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

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

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

Malicious package

angulcrjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7164

Immediate action

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

npm uninstall angulcrjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

b5ea59e181715972adb343b7dad508498951110e2e53bb8d85b0895df386ec88

ea55d2b05d27996c7659405429413f78535ac8706eba23ba6e641919cd48f91d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for angulcrjs (2 malicious versions).
If you installed it — respond
Remove angulcrjs 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 angulcrjs 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. angulcrjs 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-04884RLUA-2026-06019

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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