Which versions of karemm4 are malicious?

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

How do I remediate karemm4 if I installed it?

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

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

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

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

Malicious package

karemm4npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

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

MAL-2026-1762

Immediate action

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

npm uninstall karemm4

What this malware does

The package karemm4 was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

15df064895f12b03be4e85ddceddfb5ec1f09775b1c08dec413f532864128609

da0031492019947358400cf939e77f69a37537cca1de4fe9497a2025cd0db15b

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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