Malicious Code Injection in joint_perch_0xrequest Package
Summary
MAL-2025-104568: Malicious code in joint_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 joint_perch_0xrequest package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that aims to exploit npm's package publishing system. This package, like others in the campaign, is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the joint_perch_0xrequest package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and the undermining of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joint_perch_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 prevent the installation of the joint_perch_0xrequest package by using the following command to uninstall it: npm uninstall joint_perch_0xrequest. Additionally, ensure that your package-lock.json file is monitored for any unauthorized changes.
Conclusion
The joint_perch_0xrequest package has been compromised with malicious code that can affect the integrity of the npm ecosystem. It is crucial for developers to take immediate action by uninstalling the package and monitoring their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for joint_perch_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.
The vulnerability can lead to the pollution of the npm registry and may introduce security risks if your project relies on this package.
You should uninstall the joint_perch_0xrequest package and monitor your project for any unauthorized changes.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
