Malicious Code Injection in chemical_perch_0xrequest Package
Summary
MAL-2025-100374: Malicious code in chemical_perch_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 chemical_perch_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing capabilities, leading to potential security risks for developers and their applications.
Vulnerability Detail
The vulnerability stems from the package being associated with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk of reputation damage for developers who may unknowingly use these packages. The malicious payload can lead to further exploitation and pollution of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall chemical_perch_0xrequest
If 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, avoid using the chemical_perch_0xrequest package and consider using alternative packages that provide similar functionality without the associated risks. Always review package dependencies and their sources before installation.
Conclusion
The chemical_perch_0xrequest package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their applications. It is essential to take immediate action by removing the package and monitoring your dependencies for vulnerabilities to ensure the security of your projects.
See every vulnerability recorded for chemical_perch_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.
The vulnerability can lead to the injection of malicious code, compromising the integrity of your application and potentially leading to security breaches.
You should uninstall the package immediately using the command npm uninstall chemical_perch_0xrequest and review your project for any other affected dependencies.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.