Malicious Code Injection in traditional_chicken_0xrequest Package
Summary
MAL-2025-109797: Malicious code in traditional_chicken_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 traditional_chicken_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 known to flood the npm registry with malicious packages. The primary function of this package is to facilitate interactions within the npm ecosystem, but it has been compromised to include harmful scripts that can manipulate package metadata.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the traditional_chicken_0xrequest package. This code is designed to automatically modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential exploitation of developer reputation scores. This can result in unauthorized access to sensitive data and compromise the integrity of the software supply chain.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall traditional_chicken_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 traditional_chicken_0xrequest package and replace it with a trusted alternative that provides similar functionality. Ensure to audit your package-lock.json file to identify any indirect dependencies that may also be affected.
Conclusion
The traditional_chicken_0xrequest package poses a significant security risk due to its embedded malicious code. It is essential to remove this package from your projects and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help you stay informed about potential threats in your software.
See every vulnerability recorded for traditional_chicken_0xrequest →
FAQ
It is an npm package that has been compromised to include malicious code aimed at manipulating package metadata.
The vulnerability can lead to unauthorized modifications of your package metadata, potentially compromising your application's integrity and security.
You should immediately uninstall the package using 'npm uninstall traditional_chicken_0xrequest' and audit your dependencies for any other vulnerabilities.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check your application for vulnerabilities without any signup at the Vulert playground.
Regularly audit your dependencies, use trusted sources for packages, and keep your software updated to minimize the risk of vulnerabilities.
