Malicious Code Injection in impossible_junglefowl_0xrequest Package
Summary
MAL-2025-104013: Malicious code in impossible_junglefowl_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 'impossible_junglefowl_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 the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is aimed at inflating developer reputation scores for token rewards, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in the 'impossible_junglefowl_0xrequest' package stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This not only pollutes the npm registry but also poses risks of dependency confusion and potential exploitation of applications relying on these packages. The origin of this issue is linked to the tea.xyz token reward campaign, which has been associated with various malicious npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall impossible_junglefowl_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 'impossible_junglefowl_0xrequest' package and replace it with a trusted alternative that provides similar functionality. Always verify the integrity and source of any packages before installation.
Conclusion
The 'impossible_junglefowl_0xrequest' package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. Developers are advised to remove this package from their projects and monitor for any potential vulnerabilities using tools like Vulert. Staying informed and vigilant is crucial in maintaining the security of your applications.
See every vulnerability recorded for impossible_junglefowl_0xrequest →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to dependency confusion, potential exploitation, and pollution of the npm registry, which may affect the reliability of your application.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
Remove the package using 'npm uninstall impossible_junglefowl_0xrequest' and check your package-lock.json for any references to it.
Yes, consider using trusted alternatives that provide similar functionality, ensuring they are well-reviewed and maintained.
