Which versions of karem2 are malicious?

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

How do I remediate karem2 if I installed it?

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

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

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

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

Malicious package

karem2npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

karem2 is a confirmed malicious npm package (MAL-2026-1759) 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 karem2 (npm)

MAL-2026-1759

Immediate action

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

npm uninstall karem2

What this malware does

The package karem2 was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

760767732b0cb6dc257287e0cfe8b9a8f7f3db8021ae98bae226a3435b1bf407

7a920bfa0aa3642b248e4edf2074e57fae07f08c8824a4bc57ebd7063459559b

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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