Malicious Code Injection in gross_damselfly_0xrequest Package
Summary
MAL-2025-103391: Malicious code in gross_damselfly_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 gross_damselfly_0xrequest 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 gross_damselfly_0xrequest package stems from its inclusion in a malicious campaign that utilizes autopublish scripts to modify package.json files. This includes removing private flags, altering version numbers, and generating random package names, which leads to the pollution of the npm registry. The malicious payload can potentially allow unauthorized access to sensitive information and disrupt the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall gross_damselfly_0xrequest
If 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 gross_damselfly_0xrequest package from your project by executing the following command: npm uninstall gross_damselfly_0xrequest. This will prevent any malicious code from executing until a fix is available.
Conclusion
The gross_damselfly_0xrequest package has been identified as containing malicious code that compromises the security of the npm ecosystem. It is crucial to take immediate action by updating or removing the package to protect your application from potential threats.
See every vulnerability recorded for gross_damselfly_0xrequest →
FAQ
It is an npm package involved in the tea.xyz token reward campaign, designed to automatically publish derivative packages.
The vulnerability can lead to unauthorized modifications of your package.json file and potentially expose sensitive information.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.
If no patched version is available, it is advisable to remove the package from your project to mitigate the risk.