Malicious Code Injection in pgaool-devapptea: A Threat to npm Packages

pgaool-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107063: Malicious code in pgaool-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 package pgaool-devapptea is part of the tea.xyz token reward campaign, which has been associated with a surge of malicious packages on npm. This package is designed to facilitate token rewards through the automatic generation and publication of derivative packages. Its functionality is compromised by malicious scripts that manipulate package metadata and inflate developer reputation scores.

Vulnerability Detail

The vulnerability in pgaool-devapptea arises from the presence of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The origin of this issue is linked to a broader campaign aimed at polluting the npm registry, which can result in significant security risks for developers relying on these packages.

How To Fix

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

npm uninstall pgaool-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 avoid using this package and look for alternative solutions that do not pose security risks. Additionally, ensure that your package-lock.json is monitored for any changes using tools like Vulert.

Conclusion

The pgaool-devapptea package poses a significant security risk due to its malicious code that alters package metadata and inflates developer reputation scores. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities to maintain the integrity of your project.

See every vulnerability recorded for pgaool-devapptea →

Share this vulnerability

FAQ

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

The malicious code can alter your package metadata, leading to potential security vulnerabilities and pollution of the npm registry.

You should uninstall the package immediately and monitor your project for any unusual behavior.

Yes, tools like Vulert can help monitor your package-lock.json for vulnerabilities in real-time without requiring code access.

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

How To Fix

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

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