Malicious Code Injection in unpleasant_beaver_0xrequest Package
Summary
MAL-2025-110168: Malicious code in unpleasant_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 'unpleasant_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. This behavior poses significant risks to the integrity of the npm registry and the security of applications that rely on these packages.
Vulnerability Detail
The vulnerability in the 'unpleasant_beaver_0xrequest' package originates from its malicious intent to modify the package.json file by removing private flags and altering version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This not only pollutes the npm registry but also compromises the security of applications that may inadvertently depend on these malicious packages. The presence of autopublish scripts further exacerbates the issue by automating the malicious behavior.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall unpleasant_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 measure, you can avoid using the 'unpleasant_beaver_0xrequest' package and replace it with a trusted alternative. Review your package-lock.json file to identify any dependencies that may be affected by this vulnerability.
Conclusion
The 'unpleasant_beaver_0xrequest' package poses a significant security risk due to its malicious behavior of modifying package files and republishing variants. It is crucial to remove this package from your project and monitor your dependencies for similar vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for unpleasant_beaver_0xrequest →
FAQ
It is an npm package that is part of a malicious campaign to inflate developer reputation scores through automated package publishing.
The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.
You should uninstall the package immediately and review your project for any other potentially malicious dependencies.
You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can also check your application using the Vulert playground without needing to sign up.
Yes, tools like Vulert can help you monitor and alert you to vulnerabilities in your open-source dependencies.
