Which versions of angularks are malicious?

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

How do I remediate angularks if I installed it?

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

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

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

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

Malicious package

angularksnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7146

Immediate action

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

npm uninstall angularks

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

806e921e1ca84548e63659475212c33af1f0c6954304e5c6f84a83092e4a4ce0

f84aa00ab69699f6b91419571e99c3f89f9d62e144cbf6d81a72b679022c7b93

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for angularks (version 8.7.6).
If you installed it — respond
Remove angularks 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 angularks 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. angularks 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-04866RLUA-2026-06001

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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