Malicious Code Injection in renewed_weasel_0xrequest Package
Summary
MAL-2025-107906: Malicious code in renewed_weasel_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 renewed_weasel_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood npm with malicious packages. These packages often include scripts designed to manipulate package metadata and inflate developer reputation scores through automated publishing.
Vulnerability Detail
This vulnerability originates from the malicious intent behind the renewed_weasel_0xrequest package, which contains scripts that modify the package.json file. The scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall renewed_weasel_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, avoid using the renewed_weasel_0xrequest package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The renewed_weasel_0xrequest package poses a significant security risk due to its malicious code that modifies package metadata and repopulates the npm registry with compromised versions. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for renewed_weasel_0xrequest →
FAQ
It is an npm package that has been identified as malicious, part of a campaign to inflate developer reputation scores through automated 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 check your application for any unintended consequences of its use.
Yes, tools like Vulert can monitor your package-lock.json file to alert you in real-time about open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
