Malicious Code Injection in missing_catfish_0xrequest Package

missing_catfish_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105891: Malicious code in missing_catfish_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The missing_catfish_0xrequest 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 automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol. The package's functionality is compromised due to the presence of malicious code that alters its metadata.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the missing_catfish_0xrequest package. This code modifies the package.json file by removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants leads to pollution of the npm registry, which can affect the integrity and reliability of the ecosystem. Developers using this package may unknowingly expose their applications to security risks and reputational damage.

How To Fix

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

npm uninstall missing_catfish_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 workaround, you can avoid using the missing_catfish_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package.json file is regularly audited for any unauthorized changes.

Conclusion

The missing_catfish_0xrequest package contains malicious code that poses significant risks to developers and their applications. It is crucial to remove this package and monitor your projects for any unauthorized changes. Utilizing tools like Vulert can help maintain the security of your open-source dependencies.

See every vulnerability recorded for missing_catfish_0xrequest →

Share this vulnerability

FAQ

It is an npm package that is part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.

The malicious code modifies your package.json file and can lead to the pollution of the npm registry, potentially compromising your application's integrity.

You should uninstall the missing_catfish_0xrequest package immediately and check your project for any unauthorized changes.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall missing_catfish_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