Malicious Code Injection in jewwei-devapptea Package

jewwei-devapptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104546: Malicious code in jewwei-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 jewwei-devapptea package is part of the tea.xyz token reward campaign that has recently infiltrated the npm ecosystem. This package is designed to facilitate token rewards for developers by automatically generating and publishing derivative packages. However, it has been identified as containing malicious scripts that can compromise the integrity of the npm registry and the projects that depend on it.

Vulnerability Detail

The vulnerability in the jewwei-devapptea package stems from its inclusion of autopublish scripts that modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the pollution of the npm registry. This behavior can inflate developer reputation scores fraudulently and potentially introduce harmful code into dependent projects, posing significant security risks.

How To Fix

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

npm uninstall jewwei-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 avoid using the jewwei-devapptea package until a secure version is released. Additionally, you may want to audit your project's dependencies using npm audit to identify and mitigate any other potential vulnerabilities.

Conclusion

The jewwei-devapptea package has been identified as containing malicious code that can compromise the security of projects relying on it. It is crucial for developers to take immediate action by updating or removing the package to mitigate potential risks. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for jewwei-devapptea →

Share this vulnerability

FAQ

The jewwei-devapptea package is part of a token reward campaign that aims to incentivize developers through automatic package generation and publication.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

You should update the package to a patched version if available, or consider removing it from your project until a secure version is released.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

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

How To Fix

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

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