Which versions of angulards are malicious?

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

How do I remediate angulards if I installed it?

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

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

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

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

Malicious package

angulardsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7142

Immediate action

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

npm uninstall angulards

Malicious versions

2 flagged

1.1.48.7.6

Indicators of compromise (SHA-256)

c170b55fa56af463dc8aeeba9d731df847bfe29c64bfa875ed8344e39d5190c3

973c46cf5d81cbd56413e489629ff01d651c97007fa9afb5257dce6b713270b1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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