Malicious Code Vulnerability in eastern_crayfish_0xrequest Package
Summary
MAL-2025-101856: Malicious code in eastern_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The eastern_crayfish_0xrequest package is part of the npm ecosystem, primarily used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing system. This package is associated with the tea.xyz token reward initiative, which has led to the proliferation of numerous derivative packages that can compromise the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores for token rewards while polluting the npm registry with numerous derivative packages. The continuous republishing of these variants can lead to significant security risks, including the potential for dependency confusion and the introduction of further malicious code into projects that rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall eastern_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 workaround, you can prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Additionally, you can use the following command to uninstall the package: npm uninstall eastern_crayfish_0xrequest.
Conclusion
The eastern_crayfish_0xrequest package poses a significant security risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to be vigilant and remove such packages from their projects to maintain the integrity and security of their applications.
See every vulnerability recorded for eastern_crayfish_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the introduction of malicious code, dependency confusion, and potential security risks in your project.
You should uninstall the package immediately and monitor your project for any unusual behavior.
Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
