Critical Malicious Code Vulnerability in existdb Package

existdb Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20044: Malicious code in existdb (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

The existdb package is an npm library designed for managing and interacting with the Exist database, which is a native XML database. It provides functionalities for storing, querying, and retrieving XML data efficiently. However, the package has been found to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The existdb package has been identified to contain malicious code that can compromise the security of applications using it. This vulnerability originated from the introduction of harmful scripts within the package, which can lead to unauthorized access, data breaches, or exploitation of the host system. The malicious code can execute arbitrary commands, potentially allowing attackers to manipulate or steal sensitive information.

How To Fix

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

npm uninstall existdb

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, you can remove the existdb package from your project until a secure version is available. You can do this by executing: npm uninstall existdb. Alternatively, consider using a different package that offers similar functionalities without the associated risks.

Conclusion

The existdb package has been compromised with malicious code, posing a significant risk to applications that utilize it. It is crucial to update the package to a secure version or consider alternative solutions to mitigate potential threats. Utilizing tools like Vulert can enhance your security posture by providing real-time vulnerability monitoring.

See every vulnerability recorded for existdb →

Share this vulnerability

FAQ

The vulnerability involves malicious code embedded within the existdb package, which can lead to security breaches.

You can use the Vulert platform to monitor and alert for vulnerabilities in your application. Visit Vulert Scanner to check if your application is affected without any signup.

If immediate updates are not possible, consider uninstalling the existdb package and using an alternative solution until a secure version is released.

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software, providing a proactive approach to security.

Uninstalling existdb may affect your application's functionality if it relies on this package. Ensure you have backups and consider alternatives before proceeding.

How To Fix

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

npm uninstall existdb

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