Malicious Code Injection in muddy_jellyfish_0xrequest Package

muddy_jellyfish_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105994: Malicious code in muddy_jellyfish_0xrequest (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The muddy_jellyfish_0xrequest package is part of the npm ecosystem, often associated with token reward campaigns. It is designed to facilitate the distribution of JavaScript code for various applications. However, this package has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with derivative packages, thereby undermining the integrity of the ecosystem.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the muddy_jellyfish_0xrequest package, which is linked to the tea.xyz token reward campaign. This package includes scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. The continuous republishing of these variants leads to pollution of the npm registry, potentially affecting developers' reputations and the overall reliability of package management.

How To Fix

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

npm uninstall muddy_jellyfish_0xrequest

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, avoid using the muddy_jellyfish_0xrequest package and consider using alternative packages that provide similar functionality without the associated risks. You can also monitor your dependencies using tools like Vulert, which alerts you to vulnerabilities in real-time.

Conclusion

The muddy_jellyfish_0xrequest package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your project and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for muddy_jellyfish_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with token reward campaigns, but it has been identified as malicious due to its harmful scripts.

The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies.

You should uninstall the muddy_jellyfish_0xrequest package immediately and check for any other affected dependencies.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time without needing to access the code.

There is no patch for the muddy_jellyfish_0xrequest package; the recommended action is to uninstall it.

How To Fix

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

npm uninstall muddy_jellyfish_0xrequest

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