Malicious Code Injection in dbqlpn-devapptea: A Threat to npm Ecosystem

dbqlpn-devapptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101218: Malicious code in dbqlpn-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

dbqlpn-devapptea is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate interactions with the tea protocol, which incentivizes developers through token rewards. However, this package has been identified as malicious, containing scripts that manipulate its own metadata and flood the npm registry with derivative packages, thereby compromising the integrity of the ecosystem.

Vulnerability Detail

The vulnerability originates from the malicious design of the dbqlpn-devapptea package, which includes scripts that automatically modify the package.json file to remove private flags and change version numbers. These scripts also generate random package names and continuously republish variants, leading to pollution of the npm registry. This not only affects the reputation of legitimate developers but also poses security risks by introducing potentially harmful packages into the ecosystem.

How To Fix

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

npm uninstall dbqlpn-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 dbqlpn-devapptea package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The dbqlpn-devapptea package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata and floods the registry. It is essential for developers to remove this package and utilize tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for dbqlpn-devapptea →

Share this vulnerability

FAQ

dbqlpn-devapptea is an npm package associated with the tea.xyz token reward campaign, aimed at incentivizing developers.

The package contains scripts that modify its own metadata, remove private flags, and flood the npm registry with derivative packages.

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

If you have installed dbqlpn-devapptea, you should uninstall it immediately using the command npm uninstall dbqlpn-devapptea.

Regularly audit your dependencies, use trusted packages, and employ 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 dbqlpn-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