Malicious Code Vulnerability in dangerous_bear_requirement Package
Summary
MAL-2025-93908: Malicious code in dangerous_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 dangerous_bear_requirement package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that modifies package metadata and repackages itself under random names, leading to potential security risks.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the dangerous_bear_requirement package, which includes scripts that automatically alter the package.json file by removing private flags and changing version numbers. This behavior allows the package to continuously republish variants, polluting the npm registry and potentially compromising the integrity of other packages. The ramifications include the risk of developers unknowingly using compromised packages, leading to security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dangerous_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
Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the affected package from your project and ensuring that your dependencies are secure.
Conclusion
The dangerous_bear_requirement package poses a significant security risk due to its malicious code that alters package metadata and repackages itself. It is crucial to remove this package from your project and monitor your dependencies for vulnerabilities to maintain the integrity of your software.
See every vulnerability recorded for dangerous_bear_requirement →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages automatically.
The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.
You should uninstall the dangerous_bear_requirement package immediately and check your project for any other compromised dependencies.
Yes, you can use Vulert, which monitors and alerts 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 your application for vulnerabilities without needing to sign up.
