Malicious Code Injection in content_jay_0xrequest Package
Summary
MAL-2025-100919: Malicious code in content_jay_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 content_jay_0xrequest package is part of a broader campaign associated with the tea.xyz token reward initiative, which has been known to flood the npm ecosystem with malicious packages. This package is designed to manipulate npm's package registry by generating and publishing derivative packages with altered metadata, thereby inflating developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that can lead to significant security risks.
Vulnerability Detail
The vulnerability in the content_jay_0xrequest package stems from its inclusion in a malicious campaign that employs autopublish scripts to modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, which can lead to the pollution of the npm registry. The ramifications include potential exposure of sensitive data, unauthorized access to systems, and the degradation of the integrity of the npm ecosystem. The malicious payload is specifically designed to exploit npm's publishing mechanisms, making it a significant threat to developers and users alike.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall content_jay_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 content_jay_0xrequest package and replace it with a verified alternative. Always ensure to audit your package dependencies regularly to identify and mitigate any potential vulnerabilities.
Conclusion
The content_jay_0xrequest package poses a significant security risk due to its malicious code that alters package metadata and publishes unauthorized variants. 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 content_jay_0xrequest →
FAQ
The content_jay_0xrequest package is part of a malicious campaign that aims to manipulate the npm registry by publishing derivative packages with altered metadata.
This vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing sensitive data and compromising the integrity of your application.
You should uninstall the content_jay_0xrequest package immediately and check for any other affected packages in your project.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities in your software.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
