Malicious Code Injection in jrxtzn-devapptea: A Threat to npm Users

jrxtzn-devapptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104717: Malicious code in jrxtzn-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 package 'jrxtzn-devapptea' is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. These packages often contain scripts designed to manipulate the npm ecosystem by generating and publishing derivative packages with randomized names. This behavior not only inflates developer reputation scores but also poses significant risks to users who may unknowingly install these malicious packages.

Vulnerability Detail

The vulnerability in 'jrxtzn-devapptea' originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants. This behavior can pollute the npm registry, making it difficult for developers to find legitimate packages and potentially exposing them to security risks from malicious code.

How To Fix

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

npm uninstall jrxtzn-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 'jrxtzn-devapptea' package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package-lock.json file to identify any potentially vulnerable packages.

Conclusion

The 'jrxtzn-devapptea' package poses a significant risk due to its malicious code injection capabilities. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to protect their projects. Regular audits and the use of monitoring tools like Vulert can help mitigate these risks.

See every vulnerability recorded for jrxtzn-devapptea →

Share this vulnerability

FAQ

'jrxtzn-devapptea' is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.

The vulnerability can lead to the installation of malicious code, which may compromise your project's security and integrity.

Immediately uninstall the package using 'npm uninstall jrxtzn-devapptea' and audit your project for any other potentially vulnerable packages.

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

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

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