Malicious Code Injection in Davidjames Package: A Threat to npm Ecosystem
Summary
MAL-2025-171094: Malicious code in davidjames (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The 'davidjames' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security concerns.
Vulnerability Detail
The vulnerability in the 'davidjames' package originates from its association with the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. These actions are designed to inflate developer reputation scores fraudulently and continuously republish variants, polluting the npm registry. The ramifications include potential exposure to further malicious packages and a compromised development environment.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall davidjamesIf 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, avoid using the 'davidjames' package and consider using alternative packages that provide similar functionality without the associated risks. You can also monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.
Conclusion
The 'davidjames' package poses a significant threat to the npm ecosystem due to its malicious code injection capabilities. It is essential for developers to be vigilant, regularly update their dependencies, and utilize monitoring tools like Vulert to safeguard their applications from such vulnerabilities.
See every vulnerability recorded for davidjames →
FAQ
The 'davidjames' package is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem.
This vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You should immediately uninstall the 'davidjames' package and review your project's dependencies for any other potentially malicious packages.
You can use tools like Vulert, which allows you to monitor and receive alerts for open-source vulnerabilities in your software without needing to access the code or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
