Malicious Code Injection in dying_dingo_0xrequest Package
Summary
MAL-2025-101828: Malicious code in dying_dingo_0xrequest (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 'dying_dingo_0xrequest' package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to artificially inflate developer reputation scores for token rewards. The package's functionality is compromised by malicious scripts that manipulate its metadata.
Vulnerability Detail
The vulnerability originates from the package's design, which includes autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dying_dingo_0xrequestIf 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
Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the affected package from your project.
Conclusion
The 'dying_dingo_0xrequest' package contains a significant vulnerability that can compromise the integrity of the npm ecosystem. It is crucial to remove this package from your project and monitor for any potential impacts on your dependencies. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your open-source packages.
See every vulnerability recorded for dying_dingo_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative packages.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.
You should uninstall the package immediately using 'npm uninstall dying_dingo_0xrequest' and check for any dependencies that may be affected.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file. You can check your application for vulnerabilities at the Vulert playground without any signup.
If your application does not directly depend on 'dying_dingo_0xrequest', removing it should not affect functionality. However, ensure to check for any indirect dependencies.
