Which versions of angulkrjs are malicious?

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

How do I remediate angulkrjs if I installed it?

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

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

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

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

Malicious package

angulkrjsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

MAL-2026-7172

Immediate action

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

npm uninstall angulkrjs

Malicious versions

1 flagged

8.7.6

Indicators of compromise (SHA-256)

5a8259fbd60beddf168419d4814d2cb31d37e95a07495b9ac5283f258b61bea3

84f343fc7618d6ea48ff99237f92426b6e3c3afe0a42dbff33add2632c2663ce

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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