Which versions of kkkaremnn are malicious?

The following npm versions of kkkaremnn are flagged malicious: 1.0.0, 11.0.0. Treat any of these as compromised.

How do I remediate kkkaremnn if I installed it?

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

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

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

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

Malicious package

kkkaremnnnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

kkkaremnn is a confirmed malicious npm package (MAL-2026-1765) that executes malicious code on install (malicious versions 1.0.0, 11.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in kkkaremnn (npm)

MAL-2026-1765

Immediate action

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

npm uninstall kkkaremnn

What this malware does

The package kkkaremnn was found to contain malicious code.

Malicious versions

2 flagged

1.0.011.0.0

Indicators of compromise (SHA-256)

7e8c1aaa593d84d2c1b77a3f4a9b5fa9184d9ee163df52725d98246850b82d5b

1899924fcb632e0e93d34584c1c7dfa8068c9ba090b49aa0e896ac141ad5a2c9

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01392

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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