Malicious Code Injection in psxtzy-devapptea Package - npm Vulnerability

psxtzy-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107401: Malicious code in psxtzy-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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The psxtzy-devapptea package is part of the tea.xyz token reward campaign, which has been associated with a surge of malicious packages on the npm registry. This package is designed to facilitate token rewards through automated publishing scripts. However, it has been compromised to include malicious code that alters package metadata and floods the npm registry with derivative packages.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the psxtzy-devapptea package. This code modifies the package.json file by removing private flags, changing version numbers, and generating random package names. The intent is to inflate developer reputation scores for the tea protocol token rewards, leading to a polluted npm registry. The continuous republishing of these variants can compromise the integrity of the npm ecosystem and potentially expose users to further vulnerabilities.

How To Fix

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

npm uninstall psxtzy-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 avoid using the psxtzy-devapptea package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unintended dependencies that may include this package.

Conclusion

The psxtzy-devapptea package has been identified as containing malicious code that compromises the integrity of the npm registry and can affect your projects. It is crucial to uninstall this package and monitor your dependencies for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for psxtzy-devapptea →

Share this vulnerability

FAQ

The psxtzy-devapptea package is part of a campaign that rewards developers with tokens for publishing packages on npm. However, it has been identified as malicious.

The malicious code modifies your package.json file, potentially exposing your project to further vulnerabilities and cluttering the npm registry.

You should uninstall the psxtzy-devapptea package immediately and check for any dependencies that may be affected.

Yes, you can use Vulert to monitor and alert in real-time for open-source vulnerabilities in your software. It requires only the package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

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