Malicious Code Detected in Database-Jones Package - Security Alert

Database-Jones Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17995: Malicious code in Database-Jones (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Database-Jones is an npm package designed for database management, providing developers with tools to interact with various database systems efficiently. It is known for its user-friendly interface and robust functionality, making it a popular choice among developers. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users.

Vulnerability Detail

The vulnerability in Database-Jones originates from the inclusion of malicious code within the package. This code can potentially compromise user data, lead to unauthorized access, and disrupt normal operations. The malicious nature of the code makes it imperative for users to take immediate action to safeguard their applications and data.

How To Fix

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

npm uninstall Database-Jones

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 Database-Jones package from their projects until a secure version is confirmed. This can be done using the command: npm uninstall Database-Jones. Consider using alternative packages for database management in the interim.

Conclusion

The discovery of malicious code in the Database-Jones package highlights the importance of vigilance in managing open-source dependencies. Users are urged to update their packages promptly and consider using tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for Database-Jones →

Share this vulnerability

FAQ

The malicious code is designed to compromise user data and may allow unauthorized access to the system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.

If immediate updates are not possible, consider uninstalling the package and using alternative solutions for database management.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest versions to minimize security risks.

The vulnerability was identified by Amazon Inspector, a security assessment service.

How To Fix

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

npm uninstall Database-Jones

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