Malicious Code Injection in ugly_jellyfish_z3n: A Threat to npm Packages

ugly_jellyfish_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97073: Malicious code in ugly_jellyfish_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'ugly_jellyfish_z3n' is part of a broader campaign targeting the npm ecosystem, specifically linked to the tea.xyz token reward initiative. This package, like others in the campaign, is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores in exchange for token rewards, which poses a significant risk to the integrity of the npm registry.

Vulnerability Detail

The vulnerability in 'ugly_jellyfish_z3n' originates from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also compromises the security of applications relying on this package, potentially leading to further exploitation and misuse of developer credentials.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall ugly_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 temporary measure, you can prevent the installation of this malicious package by using the following command to uninstall it: npm uninstall ugly_jellyfish_z3n. Additionally, consider using npm audit to identify and address vulnerabilities in your project's dependencies.

Conclusion

The 'ugly_jellyfish_z3n' package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at inflating developer reputation scores. It is essential to take immediate action to remove this package and monitor your dependencies for vulnerabilities to maintain the security of your applications.

See every vulnerability recorded for ugly_jellyfish_z3n →

Share this vulnerability

FAQ

The impact includes potential exposure of sensitive data, pollution of the npm registry, and compromised application integrity.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

Immediately uninstall the package using 'npm uninstall ugly_jellyfish_z3n' and review your project's dependencies for any other vulnerabilities.

Yes, tools like Vulert can help monitor your dependencies for vulnerabilities without requiring code access or installation.

It is recommended to check for vulnerabilities regularly, ideally as part of your development workflow, to ensure your application remains secure.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall ugly_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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback