Malicious Code Injection in witty_dingo_z3n Package
Summary
MAL-2025-99002: Malicious code in witty_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 witty_dingo_z3n package is part of the npm ecosystem, often used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts, leading to potential security risks for users who inadvertently install them.
Vulnerability Detail
The vulnerability in the witty_dingo_z3n package originates from its association with the tea.xyz token reward campaign. It contains scripts that automatically modify the package.json file to remove private flags, change version numbers, and generate random package names. This results in the continuous republishing of malicious variants, polluting the npm registry and potentially compromising the integrity of applications that depend on this package.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall witty_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 temporary workaround, you can avoid using the witty_dingo_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unexpected changes or additions.
Conclusion
The witty_dingo_z3n package poses a significant security risk due to its malicious code that alters package configurations and floods the npm registry. It is essential to remove this package from your projects and monitor for any similar vulnerabilities to ensure the integrity and security of your applications.
See every vulnerability recorded for witty_dingo_z3n →
FAQ
witty_dingo_z3n is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.
The vulnerability can lead to the installation of malicious code that modifies your package.json file, potentially compromising your application's security.
You should uninstall the witty_dingo_z3n package immediately and check for any dependencies that may be affected.
Yes, you can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the packages you use.
