Malicious Code Injection in drisscroissant Package: npm Vulnerability Overview
Summary
MAL-2025-171117: Malicious code in drisscroissant (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 drisscroissant package is part of the npm ecosystem, primarily used for various JavaScript applications. It has gained notoriety due to its involvement in a token reward campaign that exploits the npm registry. This package is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. However, its malicious behavior poses significant risks to developers and users alike.
Vulnerability Detail
The vulnerability in the drisscroissant package originates from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security breaches, loss of developer reputation, and the proliferation of untrusted packages in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall drisscroissantIf 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, you can avoid using the drisscroissant package and replace it with a trusted alternative that provides similar functionality. Additionally, regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities.
Conclusion
The drisscroissant package poses a significant security risk due to its malicious code that alters package configurations and floods the npm registry with untrusted packages. It is crucial for developers to remove this package and remain vigilant about their dependencies to maintain the integrity of their projects.
See every vulnerability recorded for drisscroissant →
FAQ
drisscroissant is an npm package involved in a token reward campaign that generates and publishes malicious derivative packages.
The vulnerability can lead to the modification of your package.json file, potentially compromising your project's integrity and security.
You should uninstall the drisscroissant package immediately and monitor your project for any unusual behavior.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software without requiring code access. You can check your application using the Vulert playground.
Regularly audit your dependencies, keep them updated, and use trusted sources for package installations to minimize the risk of vulnerabilities.
