Malicious Code Injection in previous_fox_0xrequest Package
Summary
MAL-2025-107246: Malicious code in previous_fox_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 previous_fox_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to the proliferation of malicious packages designed to inflate developer reputation scores. The package's primary functionality is to facilitate requests, but it has been compromised to include harmful scripts that manipulate its own metadata.
Vulnerability Detail
The vulnerability originates from the malicious design of the previous_fox_0xrequest package, which includes scripts that automatically modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications of this vulnerability include potential exposure of sensitive information, unauthorized access to systems, and degradation of the npm ecosystem's integrity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall previous_fox_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 remove the previous_fox_0xrequest package from your project to prevent any malicious activity. Use the following command: npm uninstall previous_fox_0xrequest.
Conclusion
The previous_fox_0xrequest package has been identified as containing malicious code that can compromise the integrity of applications using it. It is crucial to take immediate action by updating or removing the package to safeguard your project from potential threats.
See every vulnerability recorded for previous_fox_0xrequest →
FAQ
It is an npm package that has been compromised to include malicious code aimed at manipulating package metadata and inflating developer reputation scores.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.
If no patched version is available, it is advisable to remove the package from your project to mitigate any risks associated with the vulnerability.
Compromised packages can lead to unauthorized access, data breaches, and can severely impact the integrity of the software ecosystem.
Vulert uses your package-lock.json file to monitor and alert in real-time for open-source vulnerabilities, ensuring you stay informed about potential risks.
