Malicious Code Injection in personal_crayfish_0xrequest Package
Summary
MAL-2025-107044: Malicious code in personal_crayfish_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 personal_crayfish_0xrequest package is a part of the npm ecosystem, often used for various JavaScript applications. It is designed to facilitate requests in a user-friendly manner. However, this package has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security risks for developers and their applications.
Vulnerability Detail
The vulnerability in the personal_crayfish_0xrequest package stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only compromises the integrity of the package but also pollutes the npm registry, potentially affecting other developers and applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall personal_crayfish_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, avoid using the personal_crayfish_0xrequest package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The personal_crayfish_0xrequest package has been identified as a vector for malicious code injection, posing significant risks to developers and their applications. Immediate action is required to remove the package and monitor for any potential impacts. Utilizing tools like Vulert can aid in maintaining the security of your software.
See every vulnerability recorded for personal_crayfish_0xrequest →
FAQ
It is an npm package designed for making requests in JavaScript applications, but it has been compromised by malicious scripts.
The vulnerability can lead to unauthorized modifications of your package.json file and the introduction of malicious code into your application.
You should uninstall the package immediately and monitor your application for any unusual behavior.
Yes, tools like Vulert can monitor your package-lock.json file to alert you in real-time for open-source vulnerabilities.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
