Which versions of angularns are malicious?

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

How do I remediate angularns if I installed it?

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

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

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

Search your lockfiles and build artifacts for angularns (version 8.7.6).

Malicious package

angularnsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

angularns is a confirmed malicious npm package (MAL-2026-7148) that executes malicious code on install (malicious version 8.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in angularns (npm)

MAL-2026-7148

Immediate action

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

npm uninstall angularns

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

9cec8c540790a51c1558c10cc0c30f3377d8e5f346874628ecdb4303bed217fc

e4ca0450ff31352632a36fa0fb83bb261bcbf79d26e66bb51f49c09e4103126f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04868RLUA-2026-06003

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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