What does the karemm6 malware do?

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

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

How do I remediate karemm6 if I installed it?

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

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

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

Malicious package

karemm6npm

Advisory published Dec 3, 2025Updated Dec 3, 2025

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

MAL-2025-191967

Immediate action

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

npm uninstall karemm6

What this malware does

The package karemm6 was found to contain malicious code.

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

d17f9161b68d61aa5f69d4d313d653d03c3256893ac716347d63dade604eea0c

7f481c97f5f745c99eb45dfa9b3744087e80ec7ac13fe1fb4043ca0274c625c3

Detection & response playbook

Malicious package

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