Malicious Code Injection in arrogant_camel_0xrequest: A Threat to npm Packages
Summary
MAL-2025-99605: Malicious code in arrogant_camel_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 package 'arrogant_camel_0xrequest' 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 creating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol, making it a significant concern for developers relying on npm for package management.
Vulnerability Detail
The vulnerability in 'arrogant_camel_0xrequest' stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly depend on these tainted packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall arrogant_camel_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 'arrogant_camel_0xrequest' package in your project. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'arrogant_camel_0xrequest' package poses a significant threat due to its malicious behavior of modifying package files and polluting the npm registry. Developers are advised to remove this package and monitor their applications for vulnerabilities using tools like Vulert. Staying informed and proactive is essential to maintaining the integrity of software projects.
See every vulnerability recorded for arrogant_camel_0xrequest →
FAQ
The primary risk is that it modifies the package.json file, potentially leading to the exposure of sensitive information and the pollution of the npm registry.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
If you have installed 'arrogant_camel_0xrequest', it is recommended to remove it immediately and check for any alternative packages that can fulfill your requirements.
Currently, there are no known patches for 'arrogant_camel_0xrequest'. It is advisable to remove the package until a safe version is released.
Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities, ensuring that developers are informed about potential risks in their applications.
