Malicious Code Injection in unhappy_dragonfly_0xrequest Package
Summary
MAL-2025-110111: Malicious code in unhappy_dragonfly_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 unhappy_dragonfly_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate interactions with APIs and manage requests effectively. However, it has been identified as vulnerable due to the presence of malicious code that compromises its integrity and the security of applications utilizing it.
Vulnerability Detail
The vulnerability stems from the package being part of a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to reputation damage and security breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall unhappy_dragonfly_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 unhappy_dragonfly_0xrequest package from your project to mitigate the risk of exploitation. You can do this by executing the following command: npm uninstall unhappy_dragonfly_0xrequest.
Conclusion
The unhappy_dragonfly_0xrequest package has been identified as containing malicious code that poses significant risks to developers and their applications. It is crucial to take immediate action to mitigate these risks by updating or removing the package. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for unhappy_dragonfly_0xrequest →
FAQ
The vulnerability involves malicious code that modifies package.json and repackages it with random names, compromising the integrity of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.
Using the compromised package can lead to security breaches, reputation damage, and the potential for your application to be flagged for using malicious code.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.
If no patched version is available, consider removing the package and replacing it with a secure alternative that fulfills the same functionality.
