What does the kkkarem malware do?

The package kkkarem was found to contain malicious code. The OpenSSF Package Analysis project identified 'kkkarem' @ 4.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 kkkarem are malicious?

The following npm versions of kkkarem are flagged malicious: 4.0.0. Treat any of these as compromised.

How do I remediate kkkarem if I installed it?

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

If kkkarem was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is kkkarem part of a known attack campaign?

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

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for kkkarem (version 4.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kkkarem across your stack and pipelines.

Malicious package

kkkaremnpm

Malicious code in kkkarem (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191948

Immediate action

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

npm uninstall kkkarem

What this malware does

The package kkkarem was found to contain malicious code.

The OpenSSF Package Analysis project identified 'kkkarem' @ 4.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

1 flagged

4.0.0

Indicators of compromise (SHA-256)

85f2f16bc0953b5738e5248e16c823f06c7e3e9805d0e85726a59b9d72a4f30b

5221f3ec4ce8c314da6ded901d34c1ef2a0f7822bbec42d09a218885c47b41b2

572e91d661be9fd444123179fc8d35037e530067487b54d3bad37d333931afe6

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for kkkarem (version 4.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging kkkarem across your stack and pipelines.
If you installed it — respond
Remove kkkarem 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 kkkarem was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks kkkarem before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. kkkarem on npm has been identified as a malicious package (version 4.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06391

Credits

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

Detect & block this

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

kkkaremnpm

What this malware does

Malicious versions

Indicators of compromise (SHA-256)

Detection & response playbook

Find it

If you installed it — respond

Did it already run?

How O3 protects you

Frequently asked questions

Campaign

Credits

Detect & block this