Malicious Code Injection in tsnzau-devapptea Package

tsnzau-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109859: Malicious code in tsnzau-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 tsnzau-devapptea package is part of the tea.xyz token reward campaign, which has been associated with a series of malicious npm packages. These packages are designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names. The functionality of this package is compromised due to the presence of malicious scripts that alter its metadata and behavior.

Vulnerability Detail

The vulnerability in the tsnzau-devapptea package originates from its association with a campaign that floods the npm registry with malicious packages. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of dependent applications.

How To Fix

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

npm uninstall tsnzau-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 tsnzau-devapptea package from your project by using the following command: npm uninstall tsnzau-devapptea. This will prevent any malicious code from executing while you seek a safer alternative.

Conclusion

The tsnzau-devapptea package contains a significant vulnerability that can compromise the integrity of applications using it. Immediate action is required to update or remove the package to prevent potential exploitation. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.

See every vulnerability recorded for tsnzau-devapptea →

Share this vulnerability

FAQ

The tsnzau-devapptea package is part of a token reward campaign that has been linked to malicious activity on the npm registry.

The vulnerability can lead to the modification of your application's package.json file, potentially compromising its integrity and security.

You should update or uninstall the tsnzau-devapptea package immediately to mitigate the risk of malicious code execution.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time by analyzing your 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 tsnzau-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