Malicious Code Injection in broken_dingo_z3n Package
Summary
MAL-2025-93446: Malicious code in broken_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 broken_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 broken_dingo_z3n package originates from its involvement in a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use 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 broken_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 measure, avoid using the broken_dingo_z3n package and consider using alternative packages that provide similar functionality without the associated risks. You can also monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.
Conclusion
The broken_dingo_z3n package poses a significant security risk due to its malicious code that modifies package files and floods the npm registry. It is crucial for developers to be aware of this vulnerability, take immediate action to remove the affected package, and utilize tools like Vulert for ongoing monitoring of their dependencies.
See every vulnerability recorded for broken_dingo_z3n →
FAQ
The broken_dingo_z3n package is an npm package involved in the tea.xyz token reward campaign, designed to automate the generation and publication of derivative packages.
The vulnerability can lead to the introduction of malicious code into your project, compromising its security and potentially affecting the integrity of your application.
If you have used the broken_dingo_z3n package, you should uninstall it immediately and replace it with a trusted alternative. Regularly check your dependencies for vulnerabilities.
Yes, you can use Vulert to monitor your project for open-source vulnerabilities by analyzing your package-lock.json file. This tool provides real-time alerts without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
