Malicious Code Injection in minimum_donkey_z3n Package
Summary
MAL-2025-88437: Malicious code in minimum_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The minimum_donkey_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate automatic publishing of derivative packages, which can inflate developer reputation scores. However, this package has been compromised, leading to significant security concerns.
Vulnerability Detail
The vulnerability originates from malicious code embedded within the minimum_donkey_z3n package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, resulting in the continuous republishing of variants to pollute the npm registry. This can lead to a compromised development environment, where developers may unknowingly use tainted packages, risking their applications' integrity and security.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall minimum_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 workaround, you can avoid using the minimum_donkey_z3n package altogether. If it is a dependency of another package, consider looking for alternative packages that provide similar functionality without the associated risks.
Conclusion
The minimum_donkey_z3n package poses a significant security risk due to its malicious code that alters package configurations and republishing behavior. It is essential to remove this package from your projects and monitor for any dependencies that may be affected. Utilizing tools like Vulert can help in identifying vulnerabilities in your applications.
See every vulnerability recorded for minimum_donkey_z3n →
FAQ
It is an npm package that was part of a token reward campaign, designed to automatically publish derivative packages.
The malicious code modifies your package.json, potentially leading to the use of compromised packages and affecting your project's integrity.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
You should uninstall the minimum_donkey_z3n package immediately and check for any dependencies that may be affected.
Yes, consider searching for other npm packages that provide similar functionality without the security risks associated with minimum_donkey_z3n.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
