Malicious Code Injection in wxbagg-devapptea: npm Package Vulnerability

wxbagg-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-111046: Malicious code in wxbagg-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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The wxbagg-devapptea package is part of the tea.xyz token reward campaign, which has been associated with a surge of malicious packages in the npm ecosystem. This package is designed to facilitate token rewards through automated publishing scripts, which can compromise the integrity of the npm registry.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the wxbagg-devapptea package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential exploitation of developer reputation scores. This poses significant risks to developers relying on the integrity of npm packages, as it can lead to the installation of compromised packages.

How To Fix

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

npm uninstall wxbagg-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 remove the wxbagg-devapptea package from your project by running the following command: npm uninstall wxbagg-devapptea. This will prevent any potential exploitation until a secure version is available.

Conclusion

The wxbagg-devapptea package contains malicious code that poses a significant risk to developers and the integrity of the npm ecosystem. It is essential to take immediate action by uninstalling the package and monitoring for any vulnerabilities in your project. Utilizing tools like Vulert can help maintain security in your software development process.

See every vulnerability recorded for wxbagg-devapptea →

Share this vulnerability

FAQ

wxbagg-devapptea is an npm package associated with the tea.xyz token reward campaign, which has been linked to malicious activities in the npm ecosystem.

The malicious code modifies your package.json file, potentially leading to the installation of compromised packages and affecting your project's integrity.

If you have installed wxbagg-devapptea, it is crucial to uninstall it immediately and check for any other affected packages in your project.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.

Regularly update your packages, monitor for vulnerabilities using tools like Vulert, and review the integrity of packages before installation.

How To Fix

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

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