Malicious Code Injection in other_manatee_0xrequest Package: npm Vulnerability Summary
Summary
MAL-2025-106818: Malicious code in other_manatee_0xrequest (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 'other_manatee_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 associated with the tea.xyz token reward system. This package, like others in the campaign, is designed to manipulate npm's registry by generating and publishing numerous derivative packages with altered names and metadata.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards, leading to a polluted npm registry. The ramifications include potential security risks for developers using these packages, as they may inadvertently include malicious code in their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall other_manatee_0xrequestIf 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 'other_manatee_0xrequest' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The 'other_manatee_0xrequest' package poses a significant security 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 a secure development environment.
See every vulnerability recorded for other_manatee_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
If you are using this package, your project may be at risk of including malicious code, which can lead to security vulnerabilities.
You should remove the 'other_manatee_0xrequest' package from your project immediately to mitigate any risks.
You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated with the latest security advisories for the packages you use.
