Malicious Code Vulnerability in outside_beaver_0xrequest Package
Summary
MAL-2025-106841: Malicious code in outside_beaver_0xrequest (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 outside_beaver_0xrequest package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior poses a significant risk to the integrity of the npm registry and can lead to the proliferation of malicious code.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior allows the package to continuously republish variants, polluting the npm registry and potentially compromising applications that depend on it. The malicious code is part of a broader trend of automated scripts that exploit npm's publishing mechanisms for nefarious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall outside_beaver_0xrequestIf 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 package from being used in your application by removing it from your package.json file and ensuring that your application does not reference it in any code. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.
Conclusion
The outside_beaver_0xrequest package poses a significant security risk due to its malicious code designed to manipulate npm's publishing system. It is essential to remove this package from your projects and monitor for any dependencies that may be affected. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for outside_beaver_0xrequest →
FAQ
It is an npm package that is part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.
You can use Vulert, which monitors your package-lock.json for vulnerabilities. Visit the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to sign up.
The risks include the potential for malicious code to be executed in your application, compromising security and data integrity.
Currently, there is no patched version of the outside_beaver_0xrequest package. The recommended action is to uninstall it.
You should review your dependencies and look for alternatives or updates that do not rely on the outside_beaver_0xrequest package.
