Malicious Code Injection in administrative_weasel_0xrequest Package
Summary
MAL-2025-99199: Malicious code in administrative_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 administrative_weasel_0xrequest package is part of the npm ecosystem, typically used for various web development tasks. However, it has been identified as part of a malicious campaign that exploits npm's package publishing system. This package has been associated with the tea.xyz token reward scheme, which aims to inflate developer reputation scores through the automatic generation and publishing of derivative packages.
Vulnerability Detail
The vulnerability in the administrative_weasel_0xrequest package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to pollute the npm registry and can lead to security risks for developers who unknowingly use these compromised packages. The origin of this vulnerability is linked to a broader trend of malicious packages flooding the npm registry, often containing scripts that automate the publication of harmful derivatives.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall administrative_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, you can avoid using the administrative_weasel_0xrequest package altogether. If it is already in use, consider replacing it with a trusted alternative package that provides similar functionality without the associated risks.
Conclusion
The administrative_weasel_0xrequest package presents a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their projects for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for administrative_weasel_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
Using this package can lead to security risks, including the potential for your project to be associated with malicious activities and the pollution of the npm registry.
You should remove the administrative_weasel_0xrequest package from your project and monitor for any updates or patches that may be released.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the packages you use.
