Malicious Code Exploit in Fellow Beaver Requirement Package
Summary
MAL-2025-94476: Malicious code in fellow_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 'fellow_beaver_requirement' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of 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 essential files and continuously republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the 'fellow_beaver_requirement' package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, often themed around Indonesian culture. The continuous republishing of these variants can lead to a significant pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially compromising the integrity of their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall fellow_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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. If you are using Vulert, you can check for vulnerabilities in your application without any installation. Simply use the Vulert playground at https://vulert.com/scanner to analyze your package-lock.json file for any affected packages.
Conclusion
The 'fellow_beaver_requirement' package poses a significant risk due to its malicious code designed to exploit the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for fellow_beaver_requirement →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the pollution of the npm registry, making it difficult to find legitimate packages and potentially compromising your application's integrity.
You should remove the 'fellow_beaver_requirement' package from your project and monitor for any updates or patches.
Yes, you can use Vulert's playground at Vulert Scanner to analyze your package-lock.json file for vulnerabilities.
Regularly monitor your dependencies and use tools like Vulert to stay informed about vulnerabilities in your open-source packages.
