Malicious Code Injection in like_egret_0xrequest Package

like_egret_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105133: Malicious code in like_egret_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 like_egret_0xrequest package is part of the npm ecosystem and is 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 that manipulate package metadata. The vulnerability arises from the package's ability to alter its own package.json file, leading to potential security risks for developers using this package.

Vulnerability Detail

The vulnerability in the like_egret_0xrequest package stems from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, thereby polluting the npm registry. This can lead to reputation inflation for malicious actors and potentially expose users to further security risks as these packages proliferate.

How To Fix

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

npm uninstall like_egret_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 like_egret_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using npm audit to identify and address vulnerabilities in your project.

Conclusion

The like_egret_0xrequest package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their projects. It is essential to remove this package and monitor for any vulnerabilities to maintain the security and integrity of your applications.

See every vulnerability recorded for like_egret_0xrequest →

Share this vulnerability

FAQ

The like_egret_0xrequest package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.

This vulnerability can lead to the proliferation of malicious packages in your project, potentially compromising security and affecting the integrity of your application.

If you have installed the like_egret_0xrequest package, it is crucial to remove it immediately and monitor your project for any further vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application using the Vulert playground without any signup.

Yes, consider researching and using alternative packages that provide similar functionalities without the associated risks of malicious code.

How To Fix

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

npm uninstall like_egret_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