Which versions of kkkaremm are malicious?

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

How do I remediate kkkaremm if I installed it?

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

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

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

Search your lockfiles and build artifacts for kkkaremm (version 1.0.0).

Malicious package

kkkaremmnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

Malicious code in kkkaremm (npm)

MAL-2026-1764

Immediate action

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

npm uninstall kkkaremm

What this malware does

The package kkkaremm was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

5dafbbc711da813f14c67c0a79c3114a5f5a422850c3a19dde838974d3a35fff

761c9b0fcddcb2caa78c82569ffeba230166d8a96f9cd21e8cee157e4708c06a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01391

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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