Malicious Code Vulnerability in civic_dingo_0xrequest Package
Summary
MAL-2025-100556: Malicious code in civic_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 civic_dingo_0xrequest package is part of the npm ecosystem, primarily associated with the tea.xyz token reward campaign. This package is designed to facilitate interactions with the tea protocol, but it has been compromised to include malicious scripts that can alter its functionality. The vulnerability stems from the package's ability to modify its own metadata, which can lead to unintended consequences for developers using it.
Vulnerability Detail
The vulnerability in the civic_dingo_0xrequest package is rooted in its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which can lead to the proliferation of derivative packages in the npm registry. The origin of this issue is linked to a campaign aimed at inflating developer reputation scores through automated publishing. The ramifications include potential security risks for applications relying on this package, as well as pollution of the npm registry with unwanted packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall civic_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 remove the civic_dingo_0xrequest package from your project if it is not essential. You can do this by executing the following command: npm uninstall civic_dingo_0xrequest. Additionally, consider using alternative packages that do not have known vulnerabilities.
Conclusion
The civic_dingo_0xrequest package has been identified as containing malicious code that poses a significant risk to applications using it. It is essential to take immediate action to update or remove the package to safeguard your project from potential vulnerabilities.
See every vulnerability recorded for civic_dingo_0xrequest →
FAQ
The civic_dingo_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign, designed for interactions with the tea protocol.
The vulnerability can lead to unauthorized modifications of your package metadata, potentially compromising your application's integrity and security.
Yes, you can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities in your software.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
If you cannot update the package, consider removing it from your project and looking for alternative packages that provide similar functionality without the associated risks.
