Malicious Code Injection in legitimate_egret-apptea Package

legitimate_egret-apptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105064: Malicious code in legitimate_egret-apptea (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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The legitimate_egret-apptea package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate various functionalities within the npm environment but has been compromised. It is known for its ability to generate and publish derivative packages, which can inflate developer reputation scores for token rewards. However, this functionality has been exploited, leading to significant vulnerabilities.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the legitimate_egret-apptea package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising other packages. This behavior can lead to reputational damage for developers and security risks for applications relying on this package.

How To Fix

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

npm uninstall legitimate_egret-apptea

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 measure, you can remove the legitimate_egret-apptea package from your project by executing: npm uninstall legitimate_egret-apptea. This will prevent the execution of the malicious code until a secure version is available.

Conclusion

The legitimate_egret-apptea package has been compromised with malicious code that alters its functionality and can lead to significant security risks. It is crucial for developers to update or remove this package to safeguard their applications. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities effectively.

See every vulnerability recorded for legitimate_egret-apptea →

Share this vulnerability

FAQ

The malicious code can lead to the pollution of the npm registry and may compromise the integrity of other packages, affecting the security of applications that depend on them.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By simply using your package-lock.json file, you can check for vulnerabilities without any installation. Visit Vulert Scanner to use the Vulert playground.

Regularly updating packages and using tools like Vulert to monitor for vulnerabilities can help prevent similar issues in the future.

If immediate updates are not possible, consider removing the package temporarily until a secure version is available.

The vulnerability was identified by Amazon Inspector, which specializes in detecting security issues in open-source packages.

How To Fix

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

npm uninstall legitimate_egret-apptea

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