Malicious Code Injection in yavjep-devapptea: A Threat to npm Ecosystem

yavjep-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-111250: Malicious code in yavjep-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The yavjep-devapptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The presence of such packages poses a significant risk to developers and users relying on npm for package management.

Vulnerability Detail

The vulnerability in yavjep-devapptea stems from its inclusion in a campaign that utilizes autopublish scripts to create and publish numerous derivative packages. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and generating random package names, which leads to pollution of the npm registry. The ramifications include potential security risks for applications using these packages, as they may inadvertently incorporate malicious code.

How To Fix

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

npm uninstall yavjep-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 workaround, you can manually remove the yavjep-devapptea package from your project by running the following command: npm uninstall yavjep-devapptea. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The yavjep-devapptea package poses a significant risk due to its malicious code that manipulates package management in the npm ecosystem. It is crucial for developers to remove this package and utilize tools like Vulert to ensure their applications remain secure from such vulnerabilities.

See every vulnerability recorded for yavjep-devapptea →

Share this vulnerability

FAQ

yavjep-devapptea is an npm package that is part of a token reward campaign, which has been identified to contain malicious code.

The malicious code can modify your package.json file, remove private flags, and publish derivative packages, potentially leading to security vulnerabilities.

You should uninstall the package immediately and monitor your project for any further vulnerabilities.

Yes, you can use Vulert to monitor your application for vulnerabilities without needing to access the code or installation.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about security advisories related to the packages you use.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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