Which versions of angultrjs are malicious?

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

How do I remediate angultrjs if I installed it?

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

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

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

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

Malicious package

angultrjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7180

Immediate action

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

npm uninstall angultrjs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

b25ea9bdbc999d1f2cd8d4691c0539480154642ceabc97ad24b58b18593ba3ca

e27f66c5ab4a6bee4c9d739c85dc3a51c82a1751435402cb9a629f53116273dc

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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