Malicious Code Injection in stormy_beaver_requirement Package
Summary
MAL-2025-96786: Malicious code in stormy_beaver_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 stormy_beaver_requirement package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can harm developers' reputations and the integrity of the registry itself.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the stormy_beaver_requirement package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants to pollute the npm registry, which can lead to significant reputational damage for developers and compromise the integrity of the npm ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been known to deploy such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall stormy_beaver_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 avoid using the stormy_beaver_requirement package until a fix is released. Additionally, you can monitor your package-lock.json file for any changes that might indicate the presence of malicious code.
Conclusion
The stormy_beaver_requirement package poses a significant risk due to its malicious code designed to exploit the npm registry. It is crucial for developers to take immediate action by updating or removing the package to protect their projects. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for stormy_beaver_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The malicious code modifies your package.json file and can lead to the publication of harmful packages, affecting your project's integrity.
You should update the package to a patched version or remove it from your project to mitigate the risk.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.
