Malicious Code Detected in karemz Package: npm Vulnerability Alert

karemz Updated 03 Dec 2025

Summary

03/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191947: Malicious code in karemz (npm). Affects karemz 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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The karemz package, version 1.0.0, is an npm package that is designed for specific functionalities within JavaScript applications. However, it has been identified as malicious due to its communication with domains linked to harmful activities and its execution of commands that may compromise system security. This vulnerability poses a significant risk to users and developers relying on this package for their projects.

Vulnerability Detail

The vulnerability in the karemz package originates from its malicious behavior, which includes communicating with a domain associated with malicious activities and executing harmful commands. This can lead to unauthorized access, data breaches, and potential system compromise. The technical aspects of this vulnerability highlight the importance of scrutinizing third-party packages, as they can introduce severe security risks into applications.

How To Fix

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

npm uninstall karemz

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

As a workaround, you can temporarily replace the karemz package with a different package that offers similar functionality. Ensure to review the security reputation of any alternative package before integrating it into your project.

Conclusion

The karemz package has been identified as malicious, posing significant risks to users and developers. Immediate action is required to remove this package and replace it with a secure alternative. Regular monitoring of dependencies and utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for karemz →

Share this vulnerability

FAQ

The karemz package is an npm package used in JavaScript applications, but it has been flagged as malicious due to its harmful behavior.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can determine if your application is affected.

If you are using the karemz package, it is crucial to uninstall it immediately and look for alternative packages that do not pose security risks.

Yes, Vulert provides a playground where you can check if your application is affected by vulnerabilities without requiring any signup.

Using malicious packages can lead to unauthorized access, data breaches, and compromise of your system's integrity, making it essential to vet third-party packages carefully.

How To Fix

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

npm uninstall karemz

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