Malicious Code Injection in eaecyp-devapptea Package

eaecyp-devapptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101839: Malicious code in eaecyp-devapptea (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 eaecyp-devapptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. These packages are designed to inflate developer reputation scores through automated publishing scripts. The functionality of this package is compromised by malicious code that alters its configuration and behavior.

Vulnerability Detail

The vulnerability in the eaecyp-devapptea package stems from malicious code that modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior is intended to pollute the npm registry and can lead to security risks such as unauthorized access and misuse of the package. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to create derivative packages with randomized names.

How To Fix

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

npm uninstall eaecyp-devapptea

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 eaecyp-devapptea package from your project to prevent any potential exploitation. This can be done using the command: npm uninstall eaecyp-devapptea.

Conclusion

The eaecyp-devapptea package contains a significant vulnerability due to malicious code that alters its configuration and behavior. It is crucial to update or remove this package to safeguard your project from potential risks. Utilizing tools like Vulert can help monitor and alert you to such vulnerabilities in real-time.

See every vulnerability recorded for eaecyp-devapptea →

Share this vulnerability

FAQ

The eaecyp-devapptea package is part of a token reward campaign that automates the publishing of npm packages to inflate developer reputation scores.

The malicious code modifies your package.json file, potentially leading to unauthorized access and misuse of your project dependencies.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. Visit Vulert Scanner to check your application without any signup.

If you cannot update the package, consider removing it from your project as a temporary measure to mitigate risks.

Further details can be found in the vulnerability report on the GitHub repository for malicious packages.

How To Fix

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

npm uninstall eaecyp-devapptea

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