Malicious Code Injection in vivid_dingo_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-97284: Malicious code in vivid_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
vivid_dingo_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which has led to the proliferation of numerous derivative packages. These packages are designed to inflate developer reputation scores by automatically generating and publishing variants with randomized names, compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in vivid_dingo_z3n 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 not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, leading to potential security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall vivid_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 affected package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before installation.
Conclusion
The discovery of malicious code in the vivid_dingo_z3n package highlights the ongoing risks associated with open-source software. It is crucial for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure the security of their projects. By taking proactive measures, developers can protect their applications from potential threats.
See every vulnerability recorded for vivid_dingo_z3n →
FAQ
vivid_dingo_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the installation of malicious code, which may compromise your project's security and integrity, potentially exposing sensitive data.
You should immediately uninstall the package using 'npm uninstall vivid_dingo_z3n' and review your project's dependencies for any other potentially compromised packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application against known vulnerabilities using the Vulert playground without any signup.
Yes, you should look for alternative packages that provide similar functionality but have a proven track record of security and reliability. Always check the package's reputation and reviews before installation.
