Malicious Code Vulnerability in perwjx-devapptea Package

perwjx-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107048: Malicious code in perwjx-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 perwjx-devapptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and continuously republish variants, thus polluting the npm ecosystem.

Vulnerability Detail

The vulnerability in the perwjx-devapptea package stems from its inclusion in a campaign that utilizes autopublish scripts to generate and publish numerous derivative packages. This malicious behavior modifies the package.json file to remove private flags, alters version numbers, and creates random package names, leading to potential security risks and pollution of the npm registry. The origin of this vulnerability is linked to the broader tea.xyz token reward initiative, which incentivizes such practices.

How To Fix

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

npm uninstall perwjx-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 workaround, you can monitor your package dependencies using tools like Vulert. By utilizing Vulert, you can check your application for vulnerabilities without requiring access to the code or installation. You can also use the Vulert playground at https://vulert.com/scanner to assess if your application is affected by this vulnerability.

Conclusion

The perwjx-devapptea package poses a significant risk due to its malicious behavior aimed at manipulating npm registry statistics. It is crucial to remove this package from your project and utilize monitoring tools like Vulert to stay informed about potential vulnerabilities in your dependencies.

See every vulnerability recorded for perwjx-devapptea →

Share this vulnerability

FAQ

The perwjx-devapptea package is part of a campaign that floods the npm registry with malicious packages aimed at manipulating developer reputation scores.

This vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your application by introducing malicious code.

You should uninstall the perwjx-devapptea package immediately and monitor your dependencies for any other malicious packages.

Regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without requiring any signup.

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