What does the karem7 malware do?

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

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

How do I remediate karem7 if I installed it?

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

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

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

Malicious package

karem7npm

Advisory published Dec 3, 2025Updated Dec 3, 2025

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

MAL-2025-191962

Immediate action

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

npm uninstall karem7

What this malware does

The package karem7 was found to contain malicious code.

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

fc2e767d0dc38af90a1b88381666d2332a206a84b4d73a078ad57de5df3d7088

1cdfd9c23b7a8d5b1d531b80431c97eb2b950c10d528d537fdd70ed62659d3d6

Detection & response playbook

Malicious package

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