Malicious Code Injection in bare_donkey_z3n Package - npm Vulnerability
Summary
MAL-2025-99798: Malicious code in bare_donkey_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 bare_donkey_z3n package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the tea.xyz token reward system. This package is designed to automatically generate and publish derivative packages with randomized names, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in the bare_donkey_z3n package originates from its inclusion in a malicious campaign that modifies the package.json file. This modification removes private flags, alters version numbers, and generates random package names, thereby allowing the package to continuously republish variants. The ramifications include potential security risks for developers using this package, as it can lead to the installation of unwanted or harmful code in their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall bare_donkey_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 remove the bare_donkey_z3n package from your project by executing the command: npm uninstall bare_donkey_z3n. This will prevent any malicious code from executing in your environment until a patched version is available.
Conclusion
The bare_donkey_z3n package poses a significant security risk due to its malicious code injection. It is crucial to take immediate action by updating or removing the package to protect your project from potential threats. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.
See every vulnerability recorded for bare_donkey_z3n →
FAQ
bare_donkey_z3n 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 installation of unwanted code, which may compromise the security and integrity of your project.
You should uninstall the package immediately and check for any other dependencies that may be affected.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without any signup.
