Malicious Code Injection in precise_fish_dumbs: A Threat to npm Packages

precise_fish_dumbs Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107188: Malicious code in precise_fish_dumbs (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 package 'precise_fish_dumbs' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The primary functionality of these packages is to engage in autopublishing, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in 'precise_fish_dumbs' originates from its malicious payload, which modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches and reputation damage.

How To Fix

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

npm uninstall precise_fish_dumbs

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 'precise_fish_dumbs' package and any packages that depend on it. Additionally, consider using a package-lock.json file to lock your dependencies to known safe versions.

Conclusion

The 'precise_fish_dumbs' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to be vigilant about their dependencies, promptly remove any compromised packages, and utilize tools like Vulert for ongoing monitoring.

See every vulnerability recorded for precise_fish_dumbs →

Share this vulnerability

FAQ

The malicious code can lead to the pollution of the npm registry, compromise the integrity of your project, and potentially expose your application to security vulnerabilities.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By using the Vulert playground, you can check if your application is affected without needing to sign up.

You should uninstall the package immediately using 'npm uninstall precise_fish_dumbs' and check for any dependencies that may be affected.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and ensure that you only install packages from trusted sources.

Signs include unexpected changes in your package.json, unusual behavior in your application, or the presence of unknown packages in your node_modules directory.

How To Fix

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

npm uninstall precise_fish_dumbs

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