Malicious Code Injection in specified_donkey_z3n Package
Summary
MAL-2025-98941: Malicious code in specified_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 specified_donkey_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary functionality of this package is to serve as a token reward mechanism; however, it has been compromised to include harmful scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the specified_donkey_z3n package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names to inflate developer reputation scores. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential security risks for developers relying on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall specified_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 prevent the installation of this malicious package by using npm's package-lock.json file to lock your dependencies. Additionally, consider using the following command to audit your project for vulnerabilities: npm audit.
Conclusion
The specified_donkey_z3n package has been identified as containing malicious code that can compromise your project's security. It is essential to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help ensure your application remains secure.
See every vulnerability recorded for specified_donkey_z3n →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, which has been compromised to include malicious scripts.
The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your project's integrity and security.
You should immediately remove the specified_donkey_z3n package from your project and check for any unauthorized changes in your package.json file.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
