Malicious Code Injection in xpfymn-devapptea Package - npm Vulnerability

xpfymn-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-111132: Malicious code in xpfymn-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The xpfymn-devapptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing numerous derivative packages with randomized names. The malicious behavior of this package poses a significant risk to developers and users relying on npm for package management.

Vulnerability Detail

The vulnerability in the xpfymn-devapptea package originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications of this vulnerability include potential exposure to malicious code, compromised developer reputation, and the risk of integrating harmful packages into projects.

How To Fix

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

npm uninstall xpfymn-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, consider removing the xpfymn-devapptea package from your project until a secure version is released. You can do this by executing the following command: npm uninstall xpfymn-devapptea.

Conclusion

The xpfymn-devapptea package presents a significant security risk due to its malicious code designed to manipulate npm's package ecosystem. Developers should take immediate action to remove the package and monitor for updates. Utilizing tools like Vulert can help maintain the security of your projects by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for xpfymn-devapptea →

Share this vulnerability

FAQ

xpfymn-devapptea is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.

The malicious code can modify your package.json file, remove private flags, and republish variants that may lead to the inclusion of harmful packages in your project.

If you have installed the xpfymn-devapptea package, it is recommended to uninstall it immediately and monitor for any updates or patches.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

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