Malicious Code Injection in disabled_damselfly_0xrequest Package
Summary
MAL-2025-101604: Malicious code in disabled_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 disabled_damselfly_0xrequest package is part of the npm ecosystem, often used in JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages typically include scripts that automate the generation and publication of derivative packages, aimed at inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in the disabled_damselfly_0xrequest package stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to security risks, including unauthorized access to sensitive data and the potential for further exploitation of affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall disabled_damselfly_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 installation of this package by using the following command to uninstall it: npm uninstall disabled_damselfly_0xrequest. Additionally, consider using npm audit to identify and address any other vulnerabilities in your project.
Conclusion
The disabled_damselfly_0xrequest package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities in real-time.
See every vulnerability recorded for disabled_damselfly_0xrequest →
FAQ
It is an npm package that has been identified as malicious, associated with the tea.xyz token reward campaign.
The vulnerability can lead to unauthorized modifications of your package.json file and potential security risks due to the pollution of the npm registry.
You should uninstall the package immediately and monitor your application for any unusual behavior.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check your application against known vulnerabilities using the Vulert playground.
Regularly audit your dependencies using tools like npm audit and consider using automated monitoring tools like Vulert to stay informed about vulnerabilities.
