Malicious Code Injection in random_jellyfish_z3n Package
Summary
MAL-2025-96180: Malicious code in random_jellyfish_z3n (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 random_jellyfish_z3n package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. The primary function of these packages is to inflate developer reputation scores in exchange for tea protocol token rewards, but they come with significant risks due to their malicious nature.
Vulnerability Detail
The vulnerability in the random_jellyfish_z3n package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with harmful packages. The ramifications include potential pollution of the npm registry and exploitation of developer reputation systems, making it crucial for developers to address this issue promptly.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall random_jellyfish_z3n
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 workaround, consider using a package-lock.json file to monitor your dependencies and ensure that no malicious packages are included. You can also utilize tools like Vulert to check for vulnerabilities in your application without requiring code access or installation. To check if your application is affected, visit the Vulert playground at https://vulert.com/scanner.
Conclusion
The random_jellyfish_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with harmful variants. It is crucial for developers to remove this package and utilize tools like Vulert to monitor for vulnerabilities in their projects.
See every vulnerability recorded for random_jellyfish_z3n →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.
You should uninstall the random_jellyfish_z3n package immediately and monitor your project for any other malicious packages.
Using tools like Vulert can help monitor your dependencies for vulnerabilities in real-time, allowing you to take action before issues arise.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.