Malicious Code Vulnerability in eva-teadev Package

eva-teadev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102272: Malicious code in eva-teadev (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 eva-teadev package is part of the npm ecosystem, often utilized for various development tasks. However, it has been identified as part of a malicious campaign associated with the tea.xyz token reward system. This package is designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability stems from the malicious code embedded within the eva-teadev package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The result is a continuous republishing of these variants, which not only clutters the npm registry but also poses risks to developers who may unknowingly use these compromised packages. The origin of this issue is linked to a broader campaign that exploits npm's publishing mechanisms for token rewards.

How To Fix

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

npm uninstall eva-teadev

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 eva-teadev package from your project by executing 'npm uninstall eva-teadev'. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The eva-teadev package has been identified as containing malicious code that can compromise the integrity of projects using it. It is essential to take immediate action by updating or removing the package to safeguard your development environment. Monitoring tools like Vulert can help keep your projects secure from similar vulnerabilities.

See every vulnerability recorded for eva-teadev →

Share this vulnerability

FAQ

The eva-teadev package is an npm package used for development purposes, but it has been compromised with malicious code.

The malicious code modifies your package.json file and can lead to the publication of unwanted packages, potentially harming your project's integrity.

If you have installed the eva-teadev package, it is recommended to uninstall it immediately and check for any updates or patches.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall eva-teadev

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