Malicious Code Injection in passive_flyingfish_0xrequest Package
Summary
MAL-2025-106935: Malicious code in passive_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 passive_flyingfish_0xrequest package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate various functionalities, but it has been compromised to include malicious scripts that manipulate its behavior. The package is primarily used for generating and publishing derivative packages, which can inflate developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability originates from malicious code embedded within the passive_flyingfish_0xrequest package. This 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. The ramifications include pollution of the npm registry, potential security risks for developers using the package, and the undermining of the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall passive_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 avoid using the passive_flyingfish_0xrequest package and look for alternative packages that provide similar functionalities without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The passive_flyingfish_0xrequest package contains malicious code that poses significant risks to developers and the npm ecosystem. It is crucial to uninstall this package and monitor your projects for vulnerabilities to maintain security and integrity.
See every vulnerability recorded for passive_flyingfish_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The malicious code can modify your package.json, remove private flags, and republish variants, leading to potential security risks and npm registry pollution.
You should uninstall the passive_flyingfish_0xrequest package immediately using the command: npm uninstall passive_flyingfish_0xrequest.
Yes, you can look for other npm packages that offer similar functionalities without the associated risks.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json. You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner.
