Critical Malicious Code Vulnerability in database-mongoose-kit Package

database-mongoose-kit Updated 10 Dec 2025

Summary

10/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192398: Malicious code in database-mongoose-kit (npm). Affected versions are not published. 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 database-mongoose-kit package is an npm library designed to facilitate interactions with MongoDB databases using Mongoose, a popular ODM (Object Data Modeling) library for Node.js. This package aims to simplify database operations and enhance developer productivity. However, it has been found to contain malicious code that compromises the security of any system where it is installed.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the database-mongoose-kit package. This code can fully compromise any computer that has the package installed or running, allowing external entities to gain control over the system. As a result, all secrets and keys stored on the affected computer should be considered compromised, necessitating immediate rotation from a secure environment. The presence of this malicious code poses significant risks, including data breaches and unauthorized access to sensitive information.

How To Fix

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

npm uninstall database-mongoose-kit

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

Currently, there are no effective workarounds to mitigate the risks posed by this vulnerability other than removing the package entirely. Users should avoid using the database-mongoose-kit package until further notice.

Conclusion

The discovery of malicious code within the database-mongoose-kit package poses a serious threat to any system using it. Immediate action is required to uninstall the package and secure any sensitive information. Users are encouraged to monitor their systems and utilize tools like Vulert to stay informed about vulnerabilities.

See every vulnerability recorded for database-mongoose-kit →

Share this vulnerability

FAQ

Immediately uninstall the package using the command: npm uninstall database-mongoose-kit and rotate all secrets and keys stored on the affected system.

The vulnerability can lead to full system compromise, allowing unauthorized access to sensitive data and potentially leading to data breaches.

No, there is currently no patched version available. The only solution is to remove the package entirely.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without any signup.

Long-term implications include potential data loss, unauthorized access to sensitive information, and damage to your organization's reputation.

How To Fix

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

npm uninstall database-mongoose-kit

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