Malicious Code Injection in innocent_lungfish_requirement Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95039: Malicious code in innocent_lungfish_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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The innocent_lungfish_requirement package is part of the npm ecosystem and has been identified as part of a malicious campaign that aims to exploit npm's package publishing system. This package, like others in the campaign, is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant risk to developers who may unknowingly use these compromised packages.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious campaign associated with the tea.xyz token reward system. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This malicious payload allows the package to continuously republish variants, polluting the npm registry and potentially leading to the installation of compromised packages by unsuspecting developers. The ramifications include loss of trust in the npm ecosystem, potential exposure to further vulnerabilities, and the risk of executing malicious code.

How To Fix

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

npm uninstall innocent_lungfish_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 workaround, you can monitor your project for any dependencies that may have been affected by this vulnerability. Use the following command to check for outdated or vulnerable packages: npm audit. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities without requiring code access or installation.

Conclusion

The innocent_lungfish_requirement package poses a significant risk due to its malicious behavior associated with the tea.xyz token reward campaign. Developers are advised to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their dependencies.

See every vulnerability recorded for innocent_lungfish_requirement →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the installation of compromised packages, which may execute malicious code, compromise your project's integrity, and pollute the npm registry.

You should uninstall the innocent_lungfish_requirement package immediately using the command: npm uninstall innocent_lungfish_requirement.

You can use the command npm audit to check for vulnerabilities in your project. Additionally, tools like Vulert can help monitor your package-lock.json for vulnerabilities in real-time.

There is no patch available for the innocent_lungfish_requirement package as it is recommended to avoid using this package altogether.

How To Fix

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

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