Malicious Code Vulnerability in fragile_mosquito_0xrequest Package
Summary
MAL-2025-102892: Malicious code in fragile_mosquito_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 fragile_mosquito_0xrequest package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the publishing of derivative packages with randomized names, which can inflate developer reputation scores in exchange for token rewards. The package's functionality is compromised by malicious scripts that alter its metadata and behavior.
Vulnerability Detail
The vulnerability originates from the package's involvement in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to a loss of control over package integrity, potential security risks for users, and degradation of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall fragile_mosquito_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 fragile_mosquito_0xrequest package from your project by executing the following command: npm uninstall fragile_mosquito_0xrequest. This will prevent any malicious code from executing until a safe version is released.
Conclusion
The fragile_mosquito_0xrequest package contains a serious vulnerability that can compromise the integrity of your project. It is crucial to take immediate action by updating or removing the package to protect your application from potential threats. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.
See every vulnerability recorded for fragile_mosquito_0xrequest →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to unauthorized modifications of your package metadata, potential security risks, and pollution of the npm registry.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.
If no patched version is available, it is advisable to remove the package from your project to mitigate risks associated with the vulnerability.
Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and remove any packages that are flagged as malicious.
