Malicious Code Injection in renewed_eel-apptea Package

renewed_eel-apptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107899: Malicious code in renewed_eel-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 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 renewed_eel-apptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem. This package is designed to facilitate token rewards by generating and publishing derivative packages. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the renewed_eel-apptea package stems from its inclusion in a campaign that utilizes autopublish scripts to create and publish numerous derivative packages with randomized names. This malicious behavior modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, thereby polluting the npm registry. The ramifications include potential security risks for developers who may unknowingly use these compromised packages, leading to reputational damage and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall renewed_eel-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 workaround, you can remove the renewed_eel-apptea package from your project by executing the following command: npm uninstall renewed_eel-apptea. This will prevent any malicious code from executing in your application until a patched version is available.

Conclusion

The renewed_eel-apptea package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to take immediate action by uninstalling the package and monitoring for updates. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities in the future.

See every vulnerability recorded for renewed_eel-apptea →

Share this vulnerability

FAQ

The renewed_eel-apptea package is part of a token reward campaign that aims to inflate developer reputation scores by flooding the npm registry with derivative packages.

The vulnerability can lead to the introduction of malicious code into your project, compromising its security and potentially affecting your reputation as a developer.

If you have installed the renewed_eel-apptea package, it is crucial to uninstall it immediately and monitor for any updates or patches that address the vulnerability.

Yes, you can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. You can check your application using the Vulert playground without any signup.

To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the packages you use.

How To Fix

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

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