Which versions of angulargs are malicious?

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

How do I remediate angulargs if I installed it?

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

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

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

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

Malicious package

angulargsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7144

Immediate action

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

npm uninstall angulargs

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

9367885725660769efb1a3b41d3a68c83fa625c986fa59161b32bd166f516f13

b889ef6187c87616261ba691d60991670a4e3d6840aef69095bc28f2610d8b7a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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