Malicious Code Injection in xehyxb-devapptea Package

xehyxb-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-111100: Malicious code in xehyxb-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The xehyxb-devapptea package is part of the tea.xyz token reward campaign, which has been associated with a surge of malicious packages on the npm registry. This package is designed to facilitate token rewards through automated publishing scripts that generate derivative packages with randomized names. Its primary function is to inflate developer reputation scores for rewards, but this has led to significant security concerns.

Vulnerability Detail

The vulnerability in the xehyxb-devapptea package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and alter version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to the unintentional exposure of sensitive data and a compromised development environment, as developers may unknowingly install these malicious packages.

How To Fix

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

npm uninstall xehyxb-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, avoid using the xehyxb-devapptea package and monitor your dependencies closely. You can also use tools like Vulert to check for vulnerabilities in your project. To do this, simply upload your package-lock.json file to Vulert's playground at https://vulert.com/scanner to see if your application is affected by this or any other vulnerabilities.

Conclusion

The xehyxb-devapptea package poses a significant security risk due to its malicious code designed to manipulate npm registry data. It is crucial to remove this package from your projects and monitor your dependencies for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for xehyxb-devapptea →

Share this vulnerability

FAQ

xehyxb-devapptea is a package associated with the tea.xyz token reward campaign, which has been linked to malicious activities on the npm registry.

The vulnerability can lead to the installation of malicious packages that may compromise your project's security and integrity.

You should uninstall the package immediately and check your project for any other affected dependencies.

Yes, Vulert can monitor your project for open-source vulnerabilities in real-time using your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without requiring an account.

How To Fix

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

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