Malicious Code Vulnerability in very_lungfish_0xrequest Package

very_lungfish_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110445: Malicious code in very_lungfish_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 very_lungfish_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate developer reputation scores through automated publishing scripts, which can lead to significant security risks.

Vulnerability Detail

The vulnerability originates from the very_lungfish_0xrequest package being associated with the tea.xyz token reward campaign. This campaign deploys malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. The continuous republishing of these variants clutters the npm registry, potentially leading to the installation of compromised packages by unsuspecting developers. The ramifications include the risk of executing malicious code and compromising the integrity of applications that depend on this package.

How To Fix

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

npm uninstall very_lungfish_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 workaround, consider using alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The very_lungfish_0xrequest package poses a significant security risk due to its association with malicious activities aimed at manipulating npm registry reputation scores. It is essential to remove this package from your projects and monitor for any similar vulnerabilities to maintain the integrity of your applications.

See every vulnerability recorded for very_lungfish_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.

If your application uses this package, it may execute malicious code that can compromise your application's security and integrity.

Currently, there is no patched version available for the very_lungfish_0xrequest package.

You should uninstall the very_lungfish_0xrequest package immediately and look for alternative packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner without any signup.

How To Fix

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

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