Malicious Code Vulnerability in varying_fly_0xrequest Package
Summary
MAL-2025-110363: Malicious code in varying_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 varying_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 automated publishing 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 integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious code embedded in the varying_fly_0xrequest package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other developers and applications relying on npm packages. The malicious payload can compromise the security of applications that inadvertently use these tainted packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall varying_fly_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 varying_fly_0xrequest package from your project by executing the command: npm uninstall varying_fly_0xrequest. This will prevent any malicious code from executing until a safe version is available.
Conclusion
The varying_fly_0xrequest package contains malicious code that poses significant risks to applications using it. It is crucial to update or remove the package to safeguard your projects. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.
See every vulnerability recorded for varying_fly_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, known for its automated publishing scripts.
The malicious code modifies your package.json, potentially leading to security vulnerabilities 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.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
If an immediate update is not possible, consider removing the package as a temporary measure to mitigate risks.