Malicious Code Injection in illegal_manatee_requirement Package

illegal_manatee_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94923: Malicious code in illegal_manatee_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 illegal_manatee_requirement package is part of the npm ecosystem, which is widely used for JavaScript development. This package is suspected to be involved in a token reward campaign that aims to inflate developer reputation scores by flooding the npm registry with derivative packages. Its functionality is compromised by malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability originates from malicious code embedded in the illegal_manatee_requirement package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of these variants. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall illegal_manatee_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 illegal_manatee_requirement package from your project by executing the following command: npm uninstall illegal_manatee_requirement. Additionally, you can monitor your project for vulnerabilities using Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.

Conclusion

The illegal_manatee_requirement package has been identified as containing malicious code that compromises the integrity of the npm registry and poses security risks to developers. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for illegal_manatee_requirement →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores by flooding the npm registry with compromised packages.

The malicious code modifies your package.json file, potentially leading to security vulnerabilities and the introduction of unwanted packages into your project.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Regularly monitor your dependencies for vulnerabilities, keep your packages updated, and use tools like Vulert to receive real-time alerts on open-source vulnerabilities.

If a patched version is not available, it is advisable to remove the package from your project and look for alternative packages that provide similar functionality.

How To Fix

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

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