Critical Malicious Code Vulnerability in dbmodeler Package

dbmodeler Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18102: Malicious code in dbmodeler (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 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 dbmodeler package is a tool designed for database modeling, providing developers with functionalities to create, visualize, and manage database schemas efficiently. It is widely used in the Node.js ecosystem for its ease of use and integration capabilities. However, recent findings have revealed that this package contains malicious code, posing significant risks to users who rely on it for their database management tasks.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the dbmodeler package. This code can potentially compromise user data, allow unauthorized access to systems, and lead to severe security breaches. The malicious code was introduced in all versions starting from 0, making it imperative for users to take immediate action to protect their applications.

How To Fix

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

npm uninstall dbmodeler

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, users can remove the dbmodeler package from their project until a secure version is released. This can be done using the command: npm uninstall dbmodeler. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The discovery of malicious code in the dbmodeler package poses a significant threat to users. Immediate action is required to update or remove the package to safeguard applications. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for dbmodeler →

Share this vulnerability

FAQ

dbmodeler is a Node.js package used for creating and managing database schemas, offering visualization and management tools for developers.

The malicious code was introduced in all versions of the dbmodeler package starting from version 0, making it a widespread issue.

The risks include potential data compromise, unauthorized access to systems, and severe security breaches that could affect users' applications.

You can use Vulert, which monitors open-source vulnerabilities in real-time. By utilizing the Vulert playground, you can check if your application is affected by this vulnerability without any signup.

If an immediate update is not possible, consider uninstalling the dbmodeler package and using alternative solutions until a secure version is available.

How To Fix

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

npm uninstall dbmodeler

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