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

pcxreu-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107007: Malicious code in pcxreu-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

The package 'pcxreu-devapptea' is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This package, like others in the campaign, utilizes scripts that can manipulate npm registry entries.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the 'pcxreu-devapptea' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The origin of this issue is linked to a broader campaign aimed at exploiting npm for token rewards, posing risks such as reputation damage for developers and potential security threats for applications relying on these packages.

How To Fix

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

npm uninstall pcxreu-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 malicious package by using npm's package-lock.json file to monitor and restrict the use of known vulnerable packages. Additionally, consider using tools like Vulert to keep track of vulnerabilities in your dependencies.

Conclusion

The 'pcxreu-devapptea' package poses a significant risk due to its malicious code designed to manipulate npm registry entries. It is crucial for developers to remove this package and utilize tools like Vulert to monitor their dependencies for vulnerabilities. Staying proactive in managing package security can help mitigate risks associated with such vulnerabilities.

See every vulnerability recorded for pcxreu-devapptea →

Share this vulnerability

FAQ

It is a package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative npm packages.

The malicious code can lead to the pollution of the npm registry and may compromise the integrity of your application by introducing untrusted packages.

You should remove the 'pcxreu-devapptea' package immediately and monitor for any updates or patches that may address the vulnerability.

Yes, Vulert allows you to monitor and alert for open-source vulnerabilities in your software using just the package-lock.json file.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about security advisories related to your packages.

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 pcxreu-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