Malicious Code Detected in davecx Package - Security Alert

davecx Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18070: Malicious code in davecx (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 davecx package is an npm library designed for various functionalities within JavaScript applications. It is commonly used for its ease of integration and utility in handling specific tasks. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users who integrate it into their projects.

Vulnerability Detail

The vulnerability in the davecx package originates from the inclusion of malicious code that can compromise the integrity of applications using it. This code may lead to unauthorized access, data breaches, or other harmful actions within the user's environment. The malicious nature of this vulnerability makes it critical for developers to address it promptly to safeguard their applications.

How To Fix

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

npm uninstall davecx

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, users can avoid using the davecx package until a secure version is released. Alternatively, consider using a different package that offers similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the davecx package highlights the importance of vigilance when using open-source libraries. Developers are urged to take immediate action to update or replace the package to protect their applications from potential threats.

See every vulnerability recorded for davecx →

Share this vulnerability

FAQ

davecx is an npm package used for various JavaScript functionalities, but it has been found to contain malicious code.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If you are using davecx, you should update to the latest patched version or consider removing it from your project until a secure version is available.

Using the davecx package can lead to unauthorized access, data breaches, and other security vulnerabilities due to the malicious code it contains.

Vulert monitors and alerts users in real-time for open-source vulnerabilities using just the package-lock.json file, providing an easy way to stay informed about potential risks.

How To Fix

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

npm uninstall davecx

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