Which versions of karemzz are malicious?

The following npm versions of karemzz are flagged malicious: 2.0.0. Treat any of these as compromised.

How do I remediate karemzz if I installed it?

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

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

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

Search your lockfiles and build artifacts for karemzz (version 2.0.0).

Malicious package

karemzznpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

Malicious code in karemzz (npm)

MAL-2026-1763

Immediate action

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

npm uninstall karemzz

What this malware does

The package karemzz was found to contain malicious code.

Malicious versions

1 flagged

2.0.0

Indicators of compromise (SHA-256)

2773feb1f5c55d507f60255a25929e471cca3bcdb3b6eba2a7beeb2ce252dd33

e2ee8177d8030d3f11012f6f6c3d5016ad370dc8dfaba1b131c9036190fab5a9

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01389

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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