Malicious Code Exploit in willing_dingo_z3n Package: npm Vulnerability Alert
Summary
MAL-2025-110931: Malicious code in willing_dingo_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 willing_dingo_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 security of the npm registry.
Vulnerability Detail
The vulnerability in the willing_dingo_z3n package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, effectively polluting the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs such packages to manipulate developer reputation scores. The ramifications include potential security risks for developers and users relying on npm packages, as well as the degradation of the npm ecosystem's reliability.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall willing_dingo_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 willing_dingo_z3n package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like Vulert to monitor for vulnerabilities.
Conclusion
The willing_dingo_z3n package poses a significant security risk due to its malicious code that alters package configurations and pollutes the npm registry. It is essential to remove this package from your project and monitor for any updates. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.
See every vulnerability recorded for willing_dingo_z3n →
FAQ
willing_dingo_z3n is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The vulnerability can compromise the integrity of your project by introducing malicious code that alters package configurations and pollutes the npm registry.
You should remove the willing_dingo_z3n package from your project and monitor for any updates or patches that may address the vulnerability.
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.
