What does the karemm5 malware do?

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

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

How do I remediate karemm5 if I installed it?

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

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

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

Malicious package

karemm5npm

Advisory published Dec 3, 2025Updated Dec 3, 2025

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

MAL-2025-191966

Immediate action

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

npm uninstall karemm5

What this malware does

The package karemm5 was found to contain malicious code.

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

c93324c96aff01b5bb7f276d1e990c3dc9839738802cc0a7f7cd42103950ec54

44b8f1c01b0b1d801421e87d707f28e16c71d39649a5cb21cda5ca7051044f2a

Detection & response playbook

Malicious package

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