Malicious Code Vulnerability in evident_crab_0xrequest Package

evident_crab_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102286: Malicious code in evident_crab_0xrequest (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The evident_crab_0xrequest package is part of a broader ecosystem of npm packages that have been associated with the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities within the npm registry but has been compromised to include malicious scripts. These scripts are intended to manipulate package metadata and inflate developer reputation scores, posing significant risks to users and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the evident_crab_0xrequest package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. The malicious payload continuously republishes these variants, which can lead to pollution of the npm registry and potential exploitation of unsuspecting developers. The origin of this issue is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with such compromised packages.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall evident_crab_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 workaround, you can avoid using the evident_crab_0xrequest package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The evident_crab_0xrequest package contains malicious code that poses significant risks to developers and the integrity of the npm ecosystem. It is essential to remove this package from your projects and monitor for any updates or alternatives. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.

See every vulnerability recorded for evident_crab_0xrequest →

Share this vulnerability

FAQ

The evident_crab_0xrequest package is an npm package that has been compromised to include malicious code aimed at manipulating package metadata and inflating developer reputation scores.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, Vulert can identify if your application is affected by this vulnerability.

If you have installed the evident_crab_0xrequest package, you should uninstall it immediately using the command: npm uninstall evident_crab_0xrequest.

Yes, you should look for alternative packages that provide similar functionality without the associated risks. Always review the package's reputation and source before installation.

Vulert uses your package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software, allowing you to stay informed about potential risks.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall evident_crab_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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback