Malicious Code Injection in uptight_fish_0xrequest Package
Summary
MAL-2025-110221: Malicious code in uptight_fish_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 uptight_fish_0xrequest package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate npm's publishing system by creating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, making the package particularly vulnerable to exploitation.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of these variants, which pollutes the npm registry and can lead to reputational damage for developers and potential security risks for users who inadvertently install these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall uptight_fish_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 manually check your package.json file for any unauthorized changes and revert them. Additionally, avoid using packages from unverified sources to minimize the risk of similar vulnerabilities.
Conclusion
The uptight_fish_0xrequest package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package and monitor your project for vulnerabilities to maintain security and integrity.
See every vulnerability recorded for uptight_fish_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, known for its malicious behavior of generating and publishing derivative packages.
The vulnerability can lead to the pollution of the npm registry, potential security risks, and damage to your developer reputation if you inadvertently use compromised packages.
You should remove the uptight_fish_0xrequest package from your project and check for any unauthorized changes in your package.json file.
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 also check your application for vulnerabilities using the Vulert playground.
Regularly audit your dependencies, use trusted sources for packages, and keep your packages updated to their latest versions.
