Malicious Code Injection in formal_jellyfish_0xrequest Package
Summary
MAL-2025-102864: Malicious code in formal_jellyfish_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 formal_jellyfish_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata and inflate developer reputation scores, posing significant risks to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the formal_jellyfish_0xrequest package stems from its inclusion in a malicious campaign that employs autopublish scripts to generate and publish derivative packages with randomized names. This behavior modifies the package.json file by removing private flags, changing version numbers, and continuously republishing variants, which can lead to pollution of the npm registry and compromise the security of dependent applications. The malicious payload can also affect the reputation of legitimate developers and create confusion within the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall formal_jellyfish_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 formal_jellyfish_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The formal_jellyfish_0xrequest package poses significant risks due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and monitor for vulnerabilities using tools like Vulert to maintain application security.
See every vulnerability recorded for formal_jellyfish_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, known for containing malicious scripts.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the security and integrity of your application.
You should uninstall the package immediately using npm uninstall formal_jellyfish_0xrequest and look for secure alternatives.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.
Yes, you should research and select packages that are well-reviewed and have a good reputation in the community, ensuring they do not have known vulnerabilities.
