Malicious Code Injection in dynamic_dove_z3n: A Threat to npm Packages
Summary
MAL-2025-94151: Malicious code in dynamic_dove_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 package dynamic_dove_z3n is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior aims to inflate developer reputation scores for rewards associated with the tea protocol, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in dynamic_dove_z3n stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly integrate these malicious packages into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dynamic_dove_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 dynamic_dove_z3n and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies to ensure that no malicious packages are included in your project.
Conclusion
The dynamic_dove_z3n package poses a significant threat due to its malicious behavior of modifying package metadata and republishing variants. Developers should take immediate action to remove this package and monitor their dependencies for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.
See every vulnerability recorded for dynamic_dove_z3n →
FAQ
dynamic_dove_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.
The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising its security and integrity.
You should uninstall the package immediately using the command: npm uninstall dynamic_dove_z3n.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
