Malicious Code Injection in djameldessert Package: A Threat to npm Users
Summary
MAL-2025-171114: Malicious code in djameldessert (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 djameldessert package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to provide developers with tools and functionalities to enhance their applications. However, it has been identified as part of a malicious campaign that exploits npm's publishing mechanisms, leading to significant security risks for users who inadvertently install it.
Vulnerability Detail
The vulnerability originates from the djameldessert package being associated with the tea.xyz token reward campaign, which floods the npm registry with malicious packages. These packages contain scripts designed to automatically generate and publish derivative packages with randomized names, effectively polluting the npm registry. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, which can lead to compromised developer reputation and potential security breaches in applications that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall djameldessertIf 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, avoid using the djameldessert package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package dependencies to ensure no malicious packages are included.
Conclusion
The djameldessert package poses a significant security risk due to its association with malicious activities on the npm registry. It is essential for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can protect their applications from potential threats.
See every vulnerability recorded for djameldessert →
FAQ
The djameldessert package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
If your application uses the djameldessert package, it may be at risk of having its reputation compromised and could potentially introduce security vulnerabilities.
You should uninstall the djameldessert package immediately using the command: npm uninstall djameldessert.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
Yes, consider looking for other npm packages that provide similar functionalities but do not have known vulnerabilities.
