Malicious Code Injection in Useful Fish Requirement Package

useful_fish_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97207: Malicious code in useful_fish_requirement (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 'useful_fish_requirement' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is designed to assist developers in managing dependencies and enhancing their applications. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that have randomized names, ultimately affecting the integrity of the ecosystem.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the 'useful_fish_requirement' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then continuously republished. This behavior is part of a broader scheme associated with the tea.xyz token reward campaign, which seeks to inflate developer reputation scores through deceptive practices. The ramifications include potential pollution of the npm registry, loss of trust in package integrity, and possible security risks for applications relying on these packages.

How To Fix

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

npm uninstall useful_fish_requirement

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 remove the 'useful_fish_requirement' package from your project by executing the command: 'npm uninstall useful_fish_requirement'. This will prevent the malicious code from executing while you seek a secure alternative.

Conclusion

The 'useful_fish_requirement' package poses a significant security risk due to the malicious code embedded within it. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing vulnerability monitoring. Awareness and proactive measures are essential to maintaining the integrity of software applications.

See every vulnerability recorded for useful_fish_requirement →

Share this vulnerability

FAQ

It is an npm package used for managing dependencies in JavaScript applications, but it has been compromised with malicious code.

The malicious code modifies your package.json, removes private flags, and generates random package names, which can lead to security vulnerabilities.

You should uninstall the package immediately and check for any updates or patches that may be available.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without signing up.

How To Fix

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

npm uninstall useful_fish_requirement

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