Malicious Code Injection in jcxgnj-devapptea Package

jcxgnj-devapptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104529: Malicious code in jcxgnj-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 jcxgnj-devapptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package is designed to facilitate token rewards for developers by generating and publishing derivative packages. However, it has been compromised, leading to significant security concerns.

Vulnerability Detail

The vulnerability originates from malicious code embedded within the jcxgnj-devapptea package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of other packages. This behavior can inflate developer reputation scores fraudulently, posing risks to the broader npm ecosystem.

How To Fix

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

npm uninstall jcxgnj-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 prevent the installation of this package by using npm's package-lock.json file to monitor dependencies. Ensure that your project does not include jcxgnj-devapptea in its dependencies. You can also use the following command to uninstall it if already installed: npm uninstall jcxgnj-devapptea.

Conclusion

The jcxgnj-devapptea package has been identified as containing malicious code that can compromise the integrity of projects using it. It is crucial to remove this package and monitor your dependencies for any vulnerabilities to maintain a secure development environment.

See every vulnerability recorded for jcxgnj-devapptea →

Share this vulnerability

FAQ

jcxgnj-devapptea is a package associated with the tea.xyz token reward campaign, which aims to incentivize developers through token rewards.

The vulnerability can lead to the modification of your package.json file, potentially compromising your project's integrity and security.

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

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground.

Regularly update your dependencies, monitor your project with tools like Vulert, and review the npm registry for any known vulnerabilities.

How To Fix

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

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