What does the karemm2 malware do?

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

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

How do I remediate karemm2 if I installed it?

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

If karemm2 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.

How do I find karemm2 across my projects, lockfiles, and CI pipelines?

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

Malicious package

karemm2npm

Advisory published Dec 3, 2025Updated Dec 3, 2025

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

MAL-2025-191964

Immediate action

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

npm uninstall karemm2

What this malware does

The package karemm2 was found to contain malicious code.

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

1.0.0

Indicators of compromise (SHA-256)

4b8bdcb09150b560d85e5ddba2a0f76f1f26e6a330c437c93d4cd8b7560a2d28

bdd5f17df1d0a4a9093ad436f4dafa59a288c2c650f7f1dff5cd36af67b5e98f

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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