Malicious Code Detected in karemm7 Package - npm Vulnerability Alert

karemm7 Updated 03 Dec 2025

Summary

03/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191968: Malicious code in karemm7 (npm). Affects karemm7 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 karemm7 package, available on npm, is designed for specific functionalities within JavaScript applications. However, it has been flagged for malicious behavior, which compromises the integrity and security of applications that utilize it. The package version 1.0.0 has been identified as particularly problematic, as it communicates with domains linked to malicious activities and executes harmful commands.

Vulnerability Detail

The vulnerability in the karemm7 package stems from its malicious code, which allows it to communicate with a domain associated with harmful activities. This behavior poses significant risks, including unauthorized access to sensitive data and potential control over the affected systems. The package's execution of commands linked to malicious behavior further exacerbates these risks, making it imperative for users to take immediate action.

How To Fix

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

npm uninstall karemm7

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 measure, you can prevent the karemm7 package from executing by removing it from your package.json file and running the command: npm uninstall karemm7. This will help safeguard your application until a secure alternative is identified.

Conclusion

The karemm7 package poses a significant security risk due to its malicious behavior. Users are strongly advised to uninstall the package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can help maintain security and alert users to potential threats.

See every vulnerability recorded for karemm7 →

Share this vulnerability

FAQ

The karemm7 package is an npm package used in JavaScript applications, but it has been identified as malicious due to its harmful behavior.

The package communicates with a domain associated with malicious activities and executes commands that can compromise system security.

You should uninstall the karemm7 package immediately to protect your application from potential threats.

Currently, there is no patched version available for karemm7. It is advised to remove the package until a secure alternative is found.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

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

npm uninstall karemm7

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