Malicious Code Injection in worrying_flyingfish_0xrequest Package
Summary
MAL-2025-111012: Malicious code in worrying_flyingfish_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 worrying_flyingfish_0xrequest package is part of a series of npm packages that have been linked to the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores in exchange for tea protocol token rewards, making the package a potential risk for developers and users alike.
Vulnerability Detail
The vulnerability in the worrying_flyingfish_0xrequest package stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random Indonesian-themed package names and continuously republishes variants, leading to pollution of the npm registry. This behavior can compromise the integrity of the npm ecosystem, allowing malicious actors to exploit the situation for their gain.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall worrying_flyingfish_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 worrying_flyingfish_0xrequest package from your project by executing the following command: npm uninstall worrying_flyingfish_0xrequest. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The worrying_flyingfish_0xrequest package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to take immediate action to mitigate this risk by updating or removing the package and utilizing tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for worrying_flyingfish_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, known for generating and publishing derivative packages.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing malicious code.
You should uninstall the worrying_flyingfish_0xrequest package immediately and monitor for any updates or patches.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
