Malicious Code Detected in davejones Package - Security Alert

davejones Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18071: Malicious code in davejones (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 davejones package is an npm library that serves various functionalities within JavaScript applications. It is widely used for its ease of integration and utility in managing specific tasks. However, it has been identified to contain malicious code, posing a significant security risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the davejones package originates from the inclusion of malicious code that can compromise the security of applications using this package. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The vulnerability is present in all versions starting from 0, making it imperative for users to take immediate action to mitigate risks.

How To Fix

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

npm uninstall davejones

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, consider removing the davejones package from your project until a secure version is released. You can do this by running the following command: npm uninstall davejones. This will help mitigate the risk of exposure to the malicious code.

Conclusion

The davejones package has been identified to contain malicious code, posing a serious security threat to applications that utilize it. Immediate action is required to update or remove the package to safeguard your application. Utilize tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for davejones →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data and compromise application integrity.

You can use Vulert to monitor and alert for vulnerabilities in your application. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Yes, it is recommended to update to the latest version of the davejones package to ensure that you are protected against the identified vulnerabilities.

If immediate updates are not possible, consider removing the package from your project as a temporary workaround to mitigate risks.

Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities, ensuring your applications remain secure.

How To Fix

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

npm uninstall davejones

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