Malicious Code Injection in chief_jellyfish_z3n Package - npm Vulnerability
Summary
MAL-2025-93534: Malicious code in chief_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 chief_jellyfish_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the chief_jellyfish_z3n package, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other packages and developers. The malicious payload can compromise the security of applications relying on this package, leading to reputational damage and security risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall chief_jellyfish_z3nIf 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 chief_jellyfish_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using npm audit to identify and address vulnerabilities in your project.
Conclusion
The chief_jellyfish_z3n package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for chief_jellyfish_z3n →
FAQ
The chief_jellyfish_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative packages.
Using this package can lead to security vulnerabilities, as it modifies critical files and repopulates the npm registry with potentially harmful packages.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
If you have installed the chief_jellyfish_z3n package, it is advised to remove it immediately and monitor your project for any unusual behavior.
Vulert monitors and alerts in real-time for open-source vulnerabilities in your software using just the package-lock.json file, ensuring you stay informed about potential risks.
