Malicious Code Detected in karem5 Package - Security Alert

karem5 Updated 03 Dec 2025

Summary

03/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191961: Malicious code in karem5 (npm). Affected versions are not published. 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 karem5 package is an npm library that is utilized in various JavaScript applications for managing specific functionalities. It is designed to streamline certain processes within the application ecosystem. However, the package has been identified as containing malicious code, posing a significant risk to users and their applications.

Vulnerability Detail

The vulnerability originates from the karem5 package, which has been flagged for containing malicious code. This code can potentially compromise the security of applications that rely on this package, leading to unauthorized access, data breaches, or other malicious activities. The specific technical details of the malicious code have not been disclosed, but its presence in the package is a serious concern for developers and users alike.

How To Fix

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

npm uninstall karem5

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 temporary workaround, you can avoid using the karem5 package in your application until a secure version is released. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The karem5 package has been identified as containing malicious code, posing a significant risk to applications that utilize it. Users are advised to remove the package and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in your software.

See every vulnerability recorded for karem5 →

Share this vulnerability

FAQ

The karem5 package is an npm library used in JavaScript applications for various functionalities. However, it has been found to contain malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If you are using the karem5 package, it is recommended to remove it from your project immediately and look for alternative packages.

Currently, there is no patched version available. It is crucial to monitor the package repository for any updates.

Using the karem5 package can expose your application to security vulnerabilities, including unauthorized access and data breaches due to the malicious code present.

How To Fix

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

npm uninstall karem5

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