Malicious Code Injection in djamelcroissant Package - npm Vulnerability
Summary
MAL-2025-171113: Malicious code in djamelcroissant (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 djamelcroissant package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package, like many others in the campaign, is designed to manipulate npm's publishing system, potentially affecting developers' reputations and the integrity of the npm registry. It is crucial for developers to be aware of such packages as they can introduce significant risks to their applications.
Vulnerability Detail
The vulnerability in the djamelcroissant package originates from its malicious intent to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is intended to inflate developer reputation scores through the automatic generation and publication of derivative packages. The continuous republishing of these variants can lead to pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially introducing security risks into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall djamelcroissantIf 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 workaround, you can temporarily avoid using the djamelcroissant package by removing it from your dependencies and replacing it with a trusted alternative. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The djamelcroissant package poses a significant risk due to its malicious behavior of modifying package metadata and republishing variants. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed about such vulnerabilities is essential for maintaining the security and integrity of your applications.
See every vulnerability recorded for djamelcroissant →
FAQ
The djamelcroissant package is an npm package that is part of a token reward campaign, which has been identified as malicious due to its behavior of modifying package metadata.
This vulnerability can lead to the pollution of the npm registry and may introduce security risks by allowing unauthorized modifications to your project's dependencies.
If you have installed the djamelcroissant package, it is advisable to remove it immediately and check for any other affected packages in your project.
You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring access to your 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.
