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

pdjblw-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107008: Malicious code in pdjblw-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

pdjblw-devapptea is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards through its functionality, which includes generating and publishing derivative packages. However, it has been compromised to include malicious scripts that can manipulate the npm registry.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the pdjblw-devapptea package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The scripts are designed to automatically publish these variants, leading to pollution of the npm registry and potential exploitation of developer reputation scores. The ramifications include unauthorized access to the npm ecosystem and the potential for further malicious activities.

How To Fix

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

npm uninstall pdjblw-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 pdjblw-devapptea package from your project by executing: npm uninstall pdjblw-devapptea. This will prevent any malicious scripts from executing until a patch is available.

Conclusion

The pdjblw-devapptea package has been identified as containing malicious code that poses a significant risk to the npm ecosystem. It is essential to take immediate action by updating or uninstalling the package to protect your project from potential exploitation.

See every vulnerability recorded for pdjblw-devapptea →

Share this vulnerability

FAQ

pdjblw-devapptea is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code can modify your package.json file, remove private flags, and publish unauthorized packages, potentially compromising your project's integrity.

If you have installed pdjblw-devapptea, you should uninstall it immediately and monitor your project for any unauthorized changes.

Yes, you can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

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

How To Fix

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

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