What does the karemm7 malware do?

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

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

How do I remediate karemm7 if I installed it?

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

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

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

Malicious package

karemm7npm

Advisory published Dec 3, 2025Updated Dec 3, 2025

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

MAL-2025-191968

Immediate action

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

npm uninstall karemm7

What this malware does

The package karemm7 was found to contain malicious code.

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

ea900c305547fbc90afe7dd06aac5431c244109fa63d688cb76e909cd3988fc4

bb23140c87c50a27ae4e614762b9639f64ae2148777774915b5cd2ba94f104a0

Detection & response playbook

Malicious package

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