Malicious Code Injection in eohfbt-devapptea Package

eohfbt-devapptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102149: Malicious code in eohfbt-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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The eohfbt-devapptea package is part of the tea.xyz token reward campaign, which has been associated with a series of malicious npm packages. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in the eohfbt-devapptea package stems from its inclusion in a campaign that floods the npm registry with malicious packages. It contains scripts that alter the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to significant security risks, including the potential for unauthorized access to sensitive data and the degradation of the npm ecosystem through pollution of the registry.

How To Fix

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

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

Currently, the best workaround is to avoid using the eohfbt-devapptea package altogether. If it is already in use, uninstall it immediately and monitor your project for any unauthorized changes. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.

Conclusion

The eohfbt-devapptea package poses a significant risk due to its malicious code designed to manipulate package files and pollute the npm registry. It is crucial to uninstall this package and monitor your project for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your open-source dependencies.

See every vulnerability recorded for eohfbt-devapptea →

Share this vulnerability

FAQ

eohfbt-devapptea is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.

The vulnerability can lead to unauthorized modifications of your package files and potentially expose your project to further security risks.

You should uninstall the eohfbt-devapptea package immediately using 'npm uninstall eohfbt-devapptea' and monitor your project for any unauthorized changes.

Yes, you can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities without requiring code access.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

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