Malicious Code Injection in standard_manatee_requirement Package
Summary
MAL-2025-96747: Malicious code in standard_manatee_requirement (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The standard_manatee_requirement package is an npm module that is part of a broader ecosystem of packages used for various development tasks. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through automated publishing of modified versions of itself and other packages.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the standard_manatee_requirement package, which is linked to the tea.xyz token reward campaign. This package contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. The continuous republishing of these variants leads to pollution of the npm registry, potentially compromising the integrity of the ecosystem and affecting developers who rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall standard_manatee_requirementIf 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 measure, you can avoid using the standard_manatee_requirement package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.
Conclusion
The standard_manatee_requirement package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their software.
See every vulnerability recorded for standard_manatee_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate npm registry and developer reputation scores.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.
You can use the Vulert playground to check for vulnerabilities in your application without requiring any installation or signup.
You should uninstall the standard_manatee_requirement package immediately and check for any other affected packages in your project.
Yes, Vulert provides a service that monitors your package-lock.json for open-source vulnerabilities in real-time.
