What does the karemz malware do?

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

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

How do I remediate karemz if I installed it?

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

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

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

Malicious package

karemznpm

Advisory published Dec 3, 2025Updated Dec 3, 2025

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

MAL-2025-191947

Immediate action

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

npm uninstall karemz

What this malware does

The package karemz was found to contain malicious code.

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

0ea2cd139758da9c9339894a56f0250a834c2fb01f4b25c9e398daef8c61c992

0210683c3480535deb828dc6e3f758815b2a57ae4a50c37dca6443ad61623aa4

Detection & response playbook

Malicious package

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