Malicious Code Injection in metropolitan_bear_requirement Package
Summary
MAL-2025-95455: Malicious code in metropolitan_bear_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 metropolitan_bear_requirement package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability originates from the malicious code embedded in the metropolitan_bear_requirement package, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly install these malicious 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 metropolitan_bear_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 metropolitan_bear_requirement package from your project by executing: npm uninstall metropolitan_bear_requirement. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The metropolitan_bear_requirement package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is essential for developers to remain vigilant, update their packages regularly, and utilize tools like Vulert to monitor for vulnerabilities effectively.
See every vulnerability recorded for metropolitan_bear_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
If your application uses the metropolitan_bear_requirement package, it may be at risk of installing malicious code that can compromise your application's security.
You should uninstall the metropolitan_bear_requirement package immediately and check for any updates or patches that may be available.
You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
