Malicious Code Injection in independent_dingo_0xrequest Package
Summary
MAL-2025-104145: Malicious code in independent_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 independent_dingo_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript applications. It was associated with the tea.xyz token reward campaign, which aimed to inflate developer reputation scores by flooding the npm registry with derivative packages. This package, like others in the campaign, is designed to automatically generate and publish variants with altered metadata, making it susceptible to malicious exploitation.
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 pollution of the npm registry. The malicious payload can compromise the integrity of applications relying on this package, potentially allowing unauthorized access or manipulation of data.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall independent_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
As a temporary workaround, you can prevent the use of this package by removing it from your dependencies. You can do this by executing the following command: npm uninstall independent_dingo_0xrequest. Additionally, consider using Vulert to monitor your project for vulnerabilities by analyzing your package-lock.json file.
Conclusion
The independent_dingo_0xrequest package contains a significant vulnerability that can compromise application security. It is crucial to update or remove the package to protect your project. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for independent_dingo_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to inflate developer reputation scores.
The vulnerability can lead to unauthorized modifications in your application's dependencies, potentially compromising its security.
Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.
If no patched version is available, it is advisable to remove the package from your project to mitigate risks.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without any signup.
