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

ccsyqj-devapptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100298: Malicious code in ccsyqj-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

ccsyqj-devapptea is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the distribution of token rewards through various scripts. However, it has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with derivative packages, potentially harming developers' reputations and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in ccsyqj-devapptea stems from its inclusion in a malicious campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This not only inflates developer reputation scores for token rewards but also modifies the package.json file to remove private flags and change version numbers. The continuous republishing of these variants pollutes the npm registry, leading to potential security risks and confusion among developers.

How To Fix

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

npm uninstall ccsyqj-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 to monitor dependencies. Ensure that your project does not include ccsyqj-devapptea in its dependencies. Additionally, consider using Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The ccsyqj-devapptea package poses a significant risk due to its malicious code that manipulates package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and monitor for vulnerabilities using tools like Vulert to maintain the integrity of their applications.

See every vulnerability recorded for ccsyqj-devapptea →

Share this vulnerability

FAQ

ccsyqj-devapptea is an npm package involved in a token reward campaign, but it has been identified as malicious due to its harmful scripts.

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

You should uninstall the package immediately using 'npm uninstall ccsyqj-devapptea' and check for any dependencies that may be affected.

Currently, there is no specific patch for this vulnerability. The best course of action is to remove the package from your project.

You can use Vulert, which monitors your package-lock.json file to alert you in real-time for any open-source vulnerabilities in your software.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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