Malicious Code Vulnerability in continued_fly_0xrequest Package
Summary
MAL-2025-100934: Malicious code in continued_fly_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 continued_fly_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 npm registry.
Vulnerability Detail
The vulnerability originates from the malicious code embedded in the continued_fly_0xrequest package. This code modifies the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. The ramifications include potential security risks for developers who unknowingly use these compromised packages, as well as damage to the reputation of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall continued_fly_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 workaround, you can avoid using the continued_fly_0xrequest package altogether. If it is already included in your project, consider removing it from your package.json and running npm install to clean up your dependencies.
Conclusion
The continued_fly_0xrequest package contains malicious code that poses a significant risk to developers and the npm ecosystem. It is crucial to remove this package from your projects and monitor for any potential vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for continued_fly_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative packages.
The malicious code modifies your package.json, removes private flags, and can lead to the publication of unwanted packages, compromising your project's integrity.
You should remove the continued_fly_0xrequest package from your project and monitor your dependencies for any malicious activity.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without signup at the Vulert playground.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the packages you use.
