What does the kkkaremn malware do?

The package kkkaremn was found to contain malicious code. The OpenSSF Package Analysis project identified 'kkkaremn' @ 11.0.0 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of kkkaremn are malicious?

The following npm versions of kkkaremn are flagged malicious: 6.0.0, 9.0.0, 11.0.0. Treat any of these as compromised.

How do I remediate kkkaremn if I installed it?

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

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

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

Search your lockfiles and build artifacts for kkkaremn (3 malicious versions).

Malicious package

kkkaremnnpm

Advisory published Dec 3, 2025Updated Dec 24, 2025

kkkaremn is a confirmed malicious npm package (MAL-2025-191969) that executes malicious code on install (malicious versions 6.0.0, 9.0.0, 11.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in kkkaremn (npm)

MAL-2025-191969

Immediate action

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

npm uninstall kkkaremn

What this malware does

The package kkkaremn was found to contain malicious code.

The OpenSSF Package Analysis project identified 'kkkaremn' @ 11.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

3 flagged

6.0.09.0.011.0.0

Indicators of compromise (SHA-256)

38d12856c4db0126dfe51c098b1f21420abc032d85ddf07e3df4a6e4cb997b17

f3c03667184e3d719c08f1d45248aca18a92737f79234f902b8951883607e188

fb4aa0f8e8d709298eaf5820d8394091385138e9d2b2aec163c56343baba0a8e

8be05818c3e6f94f41c611af1a16f1a88489f457de3d8b98cc9c4441eee9e557

7cdd385021396db7dcc36db2e4fa8aabab09ebefbde60f07e11cb34ef0fcf2cf

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06392

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

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