Malicious Code Injection in xxtmzl-devapptea Package

xxtmzl-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-111136: Malicious code in xxtmzl-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 xxtmzl-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 manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores in exchange for tea protocol token rewards, making the package a target for exploitation.

Vulnerability Detail

The vulnerability in the xxtmzl-devapptea package stems from its inclusion in a malicious campaign that employs autopublish scripts to modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. The malicious payload can compromise the integrity of the npm ecosystem, potentially affecting developers who rely on these packages for legitimate purposes.

How To Fix

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

npm uninstall xxtmzl-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 measure, avoid using the xxtmzl-devapptea package and any other packages that may be part of the tea.xyz token reward campaign. Regularly audit your project's dependencies to identify and remove any potentially harmful packages.

Conclusion

The xxtmzl-devapptea package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is essential to remove this package from your project and utilize tools like Vulert to monitor for vulnerabilities in your dependencies.

See every vulnerability recorded for xxtmzl-devapptea →

Share this vulnerability

FAQ

xxtmzl-devapptea is an npm package associated with a token reward campaign that has been found to contain malicious code.

The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies.

You should uninstall the xxtmzl-devapptea package immediately using the command: npm uninstall xxtmzl-devapptea.

Yes, tools like Vulert can monitor your project for open-source vulnerabilities using just the package-lock.json file.

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

How To Fix

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

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