Malicious Code Injection in unwilling_lobster_requirement Package
Summary
MAL-2025-97180: Malicious code in unwilling_lobster_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 unwilling_lobster_requirement package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is implicated in a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores for token rewards associated with the tea.xyz protocol. The malicious nature of this package lies in its ability to modify critical files and republish variants, thus polluting the npm registry.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the unwilling_lobster_requirement package. This code is designed to automatically modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, which can lead to a significant pollution of the npm registry, making it difficult for developers to find legitimate packages. The origin of this vulnerability is linked to a broader campaign that exploits the npm ecosystem for nefarious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall unwilling_lobster_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 workaround, you can remove the unwilling_lobster_requirement package from your project by executing the following command: npm uninstall unwilling_lobster_requirement. This will prevent any malicious code from executing in your application until a patch is available.
Conclusion
The unwilling_lobster_requirement package poses a significant risk due to its malicious code designed to exploit the npm registry. It is essential for developers to stay vigilant, regularly update their packages, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can protect your applications from potential threats.
See every vulnerability recorded for unwilling_lobster_requirement →
FAQ
The unwilling_lobster_requirement package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
This vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your application by introducing malicious code.
You should uninstall the package immediately and check for any updates or patches that may address the vulnerability.
Yes, you can use Vulert to monitor your application for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
