What does the karemm1 malware do?

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

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

How do I remediate karemm1 if I installed it?

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

If karemm1 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 karemm1 across my projects, lockfiles, and CI pipelines?

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

Malicious package

karemm1npm

Advisory published Dec 3, 2025Updated Dec 3, 2025

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

MAL-2025-191963

Immediate action

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

npm uninstall karemm1

What this malware does

The package karemm1 was found to contain malicious code.

The OpenSSF Package Analysis project identified 'karemm1' @ 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)

0f87456104eeeb78cac0cdb21d017530153ecae93b9e675b0d14f83d365c7b45

48612b0b1dd13d62c19284c76e6d5c16b29512f42c35ba20ad6243ba89c6d647

Detection & response playbook

Malicious package

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