Malicious Code Injection in dpnbzc-devapptea: A Threat to npm Users

dpnbzc-devapptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101752: Malicious code in dpnbzc-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

dpnbzc-devapptea is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards for developers by generating and publishing derivative packages. However, it has been identified as containing malicious scripts that can compromise the integrity of the npm registry and the projects that depend on it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the dpnbzc-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 to pollute the npm registry, potentially leading to reputation inflation for developers and compromising the security of dependent projects. The origin of this vulnerability is linked to a broader campaign that exploits npm's publishing mechanisms.

How To Fix

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

npm uninstall dpnbzc-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 measure, you can avoid using the dpnbzc-devapptea package and any of its derivatives. Regularly audit your package dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The dpnbzc-devapptea package poses a significant risk due to its malicious code that can alter project configurations and pollute the npm registry. It is essential for developers to take immediate action by removing this package and monitoring their dependencies for vulnerabilities.

See every vulnerability recorded for dpnbzc-devapptea →

Share this vulnerability

FAQ

dpnbzc-devapptea is an npm package involved in the tea.xyz token reward campaign, which aims to incentivize developers through token rewards.

The malicious code can modify your package.json, remove private flags, and create numerous derivative packages, potentially compromising your project's integrity and security.

You should uninstall the dpnbzc-devapptea package immediately using the command npm uninstall dpnbzc-devapptea.

You can use tools like npm audit or services like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without 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 dpnbzc-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