Malicious Code Injection in protestant_crawdad_z3n Package
Summary
MAL-2025-107379: Malicious code in protestant_crawdad_z3n (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 protestant_crawdad_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. It is often utilized for various functionalities within applications, but this particular package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of derivative packages. This vulnerability poses significant risks to developers and users by polluting the npm registry with harmful packages.
Vulnerability Detail
The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which floods npm with malicious packages. These packages contain scripts designed to automatically generate and publish derivative packages with randomized names, effectively modifying the package.json file to remove private flags and change version numbers. This behavior can lead to the proliferation of malicious code in the npm registry, potentially compromising 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 protestant_crawdad_z3nIf 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, you can avoid using the protestant_crawdad_z3n package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package-lock.json file to identify and remove any malicious packages.
Conclusion
The protestant_crawdad_z3n package poses a significant security risk due to its association with malicious activities aimed at inflating developer reputation scores. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the security of their applications.
See every vulnerability recorded for protestant_crawdad_z3n →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You should remove the protestant_crawdad_z3n package from your project and monitor for any updates or patches.
You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Yes, tools like npm audit and Vulert can help identify and manage vulnerabilities in your npm packages.
