Which versions of karem6 are malicious?

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

How do I remediate karem6 if I installed it?

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

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

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

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

Malicious package

karem6npm

Advisory published Dec 23, 2025Updated Jan 2, 2026

karem6 is a confirmed malicious npm package (MAL-2025-192820) 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 karem6 (npm)

MAL-2025-192820

Immediate action

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

npm uninstall karem6

What this malware does

The package karem6 was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

9e194520214ed8a406de228a27a71efb838d4e827a68af04ac69a547fb72330d

93bf9e5fd5d1d17e88170e073123f6e2304a0ebe5782a3da68a6fe6c4ea3e8a7

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for karem6 (version 1.0.0).
If you installed it — respond
Remove karem6 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 karem6 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. karem6 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-2025-06387

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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