Malicious Code Vulnerability in karemm4 Package

karemm4 Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1762: Malicious code in karemm4 (npm). Affects karemm4 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 karemm4 package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for its ease of integration and utility functions. However, it has been identified as having a serious vulnerability that exposes users to potential malicious code execution, compromising application security.

Vulnerability Detail

The vulnerability in the karemm4 package stems from the inclusion of malicious code that can execute unauthorized actions within the user's environment. This issue was reported by ReversingLabs and affects version 1.0.0 of the package. The ramifications of this vulnerability include unauthorized access to sensitive data, potential data loss, and the ability for attackers to manipulate the application’s behavior. Users of this package should be aware of the risks associated with its use and take immediate action to mitigate these threats.

How To Fix

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

npm uninstall karemm4

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

If an immediate update is not possible, consider removing the karemm4 package from your project until a secure version is released. You can uninstall it using the command: npm uninstall karemm4.

Conclusion

The karemm4 package has been identified with a serious vulnerability due to malicious code. Users are strongly advised to update or remove the package to protect their applications from potential threats. Monitoring tools like Vulert can assist in identifying vulnerabilities in real-time.

See every vulnerability recorded for karemm4 →

Share this vulnerability

FAQ

The karemm4 package is an npm library used in JavaScript applications for various functionalities.

The karemm4 package contains malicious code that can execute unauthorized actions, posing a security risk.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

As a temporary measure, you should uninstall the karemm4 package from your project to mitigate the risk.

The vulnerability was reported by ReversingLabs, a security research firm specializing in malware analysis.

How To Fix

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

npm uninstall karemm4

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