Malicious Code Detected in karem1 Package: npm Vulnerability Alert

karem1 Updated 03 Dec 2025

Summary

03/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191958: Malicious code in karem1 (npm). Affects karem1 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The karem1 package, available on npm, is designed for JavaScript applications. It is intended to provide specific functionalities within the npm ecosystem. However, the package has been flagged for malicious activity, raising concerns about its safety and integrity. Users of this package should be aware of its potential risks, especially in production environments.

Vulnerability Detail

The karem1 package version 1.0.0 has been identified as malicious due to its communication with domains linked to harmful activities and its execution of commands associated with malicious behavior. This vulnerability poses significant risks, including unauthorized access to systems, data breaches, and potential exploitation of the affected applications.

How To Fix

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

npm uninstall karem1

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 disable any functionalities that rely on the karem1 package until a safe alternative is implemented. This can be done by commenting out the relevant code sections in your application that utilize karem1.

Conclusion

The karem1 package has been identified as a security threat due to its malicious behavior. Users are advised to uninstall the package and seek safer alternatives to protect their applications from potential vulnerabilities. Regular monitoring of dependencies is essential to maintain application security.

See every vulnerability recorded for karem1 →

Share this vulnerability

FAQ

The karem1 package is a JavaScript library available on npm, designed for specific functionalities in applications.

It is considered malicious because it communicates with domains associated with harmful activities and executes commands that can compromise system security.

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

If you have installed karem1, it is crucial to uninstall it immediately and look for alternative packages that do not pose security risks.

No patches are available for karem1 as it has been flagged as malicious. The best course of action is to remove the package entirely.

How To Fix

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

npm uninstall karem1

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