Malicious Code Injection in exciting_chicken_0xrequest Package
Summary
MAL-2025-102340: Malicious code in exciting_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 exciting_chicken_0xrequest package is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. The malicious nature of this package lies in its ability to modify critical files and republish itself, thereby polluting the npm registry.
Vulnerability Detail
This vulnerability originates from the package's design, which includes autopublish scripts that remove private flags from package.json, alter version numbers, and generate random package names. This behavior can lead to significant issues, including the risk of unintentional exposure of sensitive data, the proliferation of malicious packages in the npm registry, and potential damage to the reputation of developers associated with these packages. The technical aspects include the modification of package.json and the continuous republishing of variants, which can overwhelm the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall exciting_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 exciting_chicken_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can implement strict package management practices to monitor and control the packages being used in your project.
Conclusion
The exciting_chicken_0xrequest package poses a significant risk due to its malicious code that modifies essential files and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package and adopt best practices for dependency management to safeguard their projects.
See every vulnerability recorded for exciting_chicken_0xrequest →
FAQ
It is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through automated package publishing.
The vulnerability can lead to the exposure of sensitive data and the introduction of malicious packages into your project, potentially compromising its integrity.
You should immediately remove the exciting_chicken_0xrequest package from your project and monitor your dependencies for any other malicious packages.
Yes, tools like Vulert can help monitor your project for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
