Malicious Code Detected in karemm3 Package: npm Vulnerability Alert

karemm3 Updated 03 Dec 2025

Summary

03/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191965: Malicious code in karemm3 (npm). Affects karemm3 versions 1.0.0. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The karemm3 package, version 1.0.0, is an npm package that has been identified as malicious. It is designed to facilitate certain functionalities within JavaScript applications but has been compromised to perform harmful actions. This vulnerability poses a significant risk to users who may unknowingly integrate this package into their projects, exposing them to potential security threats.

Vulnerability Detail

The karemm3 package has been flagged as malicious due to its communication with a domain linked to malicious activities and its execution of commands associated with harmful behavior. This vulnerability originates from the package's design, which allows it to perform unauthorized actions, potentially leading to data breaches, system compromise, or further exploitation of the user's environment.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall karemm3

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

Currently, there are no specific workarounds to mitigate the risks posed by the karemm3 package. The best course of action is to remove the package entirely from your project.

Conclusion

The karemm3 package has been identified as a malicious threat within the npm ecosystem, executing harmful commands and communicating with malicious domains. Users are strongly advised to uninstall this package and monitor their applications for any vulnerabilities using tools like Vulert. Staying informed and proactive is crucial in maintaining the security of your software.

See every vulnerability recorded for karemm3 →

Share this vulnerability

FAQ

The karemm3 package is an npm package that has been identified as malicious, executing harmful commands and communicating with malicious domains.

You can check if your application is affected by using the Vulert playground at Vulert Scanner, which allows you to monitor for open-source vulnerabilities without requiring any signup.

If you have installed karemm3, you should uninstall it immediately using the command 'npm uninstall karemm3' to protect your application from potential threats.

While specific alternatives are not mentioned, it is advisable to look for reputable packages that offer similar functionality without the associated risks.

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software, ensuring you stay informed about potential threats.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall karemm3

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback