Malicious Code Vulnerability in karem9 Package

karem9 Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1761: Malicious code in karem9 (npm). Affects karem9 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 karem9 package is a JavaScript library available through npm, designed for various functionalities within Node.js applications. It is utilized by developers for its ease of integration and lightweight nature. However, the package has been identified to contain malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the karem9 package stems from the inclusion of malicious code that can compromise the integrity of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this vulnerability was reported by ReversingLabs, highlighting its potential to affect users who have installed version 1.0.0 of the package.

How To Fix

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

npm uninstall karem9

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 replacing the karem9 package with an alternative library that provides similar functionality without the associated risks. Always ensure to review the security history of any new package before integration.

Conclusion

The karem9 package has been identified as containing malicious code that poses a significant risk to applications utilizing it. Immediate action is required to uninstall the package and consider alternatives to safeguard your application. Regular monitoring for vulnerabilities using tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for karem9 →

Share this vulnerability

FAQ

The karem9 package is a JavaScript library available on npm, used for various functionalities in Node.js applications.

The vulnerability involves malicious code that can compromise application security, leading to potential unauthorized access or data breaches.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

You should uninstall the karem9 package immediately using the command npm uninstall karem9 and consider using an alternative library.

The vulnerability was reported by ReversingLabs, a cybersecurity firm specializing in threat intelligence.

How To Fix

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

npm uninstall karem9

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