Malicious Code Injection in definite_crow_z3n Package - npm Vulnerability
Summary
MAL-2025-93950: Malicious code in definite_crow_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 definite_crow_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which modifies the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only affects the affected package but also poses a risk to the broader npm ecosystem by creating confusion and potentially leading to the installation of compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall definite_crow_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 workaround, you can avoid using the definite_crow_z3n package altogether. If it is a dependency of another package, consider looking for alternative packages that do not have this vulnerability.
Conclusion
The definite_crow_z3n package has been identified as containing malicious code that poses a significant risk to users and the npm ecosystem. It is crucial to remove this package from your projects and monitor for any future vulnerabilities to maintain the integrity and security of your applications.
See every vulnerability recorded for definite_crow_z3n →
FAQ
The definite_crow_z3n package is part of the npm ecosystem, associated with the tea.xyz token reward campaign, and is designed to automate the generation and publication of packages.
The vulnerability can lead to the installation of malicious code, which may compromise your project's integrity and security, as well as pollute the npm registry.
If you have installed the definite_crow_z3n package, you should uninstall it immediately using npm uninstall definite_crow_z3n and check for any dependencies that may rely on it.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.
Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and review your package-lock.json file to identify any potential risks.
