Malicious Code Injection in Confused Weasel 0xRequest Package
Summary
MAL-2025-100852: Malicious code in confused_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 'confused_weasel_0xrequest' package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate npm's registry by automatically publishing derivative packages with randomized names. The primary function of this package is to facilitate the generation of these derivative packages, which are often used to inflate developer reputation scores for token rewards. However, this functionality comes with significant security risks.
Vulnerability Detail
The vulnerability in the 'confused_weasel_0xrequest' package stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. This allows the package to generate random names for derivative packages, which are then continuously republished to pollute the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been associated with a surge of malicious npm packages. The ramifications include potential exposure of sensitive data, unauthorized access to systems, and degradation of the npm registry's integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall confused_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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. If you suspect that the package is already installed, you can remove it using the command: npm uninstall confused_weasel_0xrequest.
Conclusion
The 'confused_weasel_0xrequest' package poses a significant security risk due to its malicious payload that alters package metadata and repopulates the npm registry with harmful derivatives. It is crucial to remove this package and monitor your dependencies to maintain the integrity of your applications.
See every vulnerability recorded for confused_weasel_0xrequest →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.
The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing sensitive data and compromising your application's integrity.
You should uninstall the 'confused_weasel_0xrequest' package immediately and monitor your dependencies for any malicious activity.
Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without any signup.
