Malicious Code Vulnerability in karem6 Package

karem6 Updated 24 Dec 2025

Summary

23/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192820: Malicious code in karem6 (npm). Affects karem6 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 karem6 package is an npm library that serves various functionalities within JavaScript applications. It is designed to facilitate specific tasks, but like many open-source packages, it can be susceptible to vulnerabilities if not properly maintained. The recent discovery of malicious code in version 1.0.0 raises significant concerns for developers relying on this package for their projects.

Vulnerability Detail

The vulnerability identified in the karem6 package is characterized by the presence of malicious code that could potentially compromise the security of applications utilizing this package. This issue originated from a malicious actor who injected harmful code into the package, which can lead to unauthorized access, data breaches, or other malicious activities. The technical aspects of this vulnerability include the exploitation of the package's functionality to execute harmful operations without the user's consent.

How To Fix

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

npm uninstall karem6

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, consider using alternative packages that offer similar functionalities. You can also implement additional security measures in your application to mitigate risks while you transition away from using karem6.

Conclusion

The discovery of malicious code in the karem6 package highlights the importance of maintaining security in open-source software. Developers should take immediate action to remove the affected package and consider alternatives to safeguard their applications.

See every vulnerability recorded for karem6 →

Share this vulnerability

FAQ

Karem6 is an npm package 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 real-time. Check your application using the Vulert playground at Vulert Scanner without any signup.

It is recommended to uninstall the karem6 package and look for alternative libraries that do not pose security risks.

Currently, there is no patched version available for the karem6 package. Users should remove the package until a secure alternative is found.

Using a package with malicious code can lead to unauthorized access, data breaches, and other harmful activities that compromise the security of your application.

How To Fix

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

npm uninstall karem6

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