Malicious Code Injection in aadvuo-devapptea Package

aadvuo-devapptea Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99028: Malicious code in aadvuo-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

The aadvuo-devapptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The primary function of this package is to facilitate the distribution of token rewards, but its malicious behavior poses significant risks to developers and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the aadvuo-devapptea package stems from its inclusion in a campaign that deploys autopublish scripts to modify package.json files. These scripts remove private flags, alter version numbers, and generate random package names, leading to the pollution of the npm registry. This behavior can result in developers unknowingly using compromised packages, potentially exposing their applications to security risks and undermining the trustworthiness of the npm ecosystem.

How To Fix

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

npm uninstall aadvuo-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 the aadvuo-devapptea package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies to ensure that no malicious packages are included in your project.

Conclusion

The aadvuo-devapptea package presents a significant security risk due to its malicious code designed to manipulate npm's registry. Developers are advised to remove this package and regularly audit their dependencies to maintain the integrity of their projects. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.

See every vulnerability recorded for aadvuo-devapptea →

Share this vulnerability

FAQ

The aadvuo-devapptea package is part of a campaign that aims to manipulate npm's package registry for token rewards, but it contains malicious code that can compromise your project.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities. Visit Vulert Scanner to check your application without any signup.

Using the aadvuo-devapptea package can lead to the inclusion of malicious code in your project, potentially compromising security and integrity.

Regularly audit your dependencies and utilize tools like Vulert to monitor for vulnerabilities in real-time.

Immediately uninstall the aadvuo-devapptea package and review your project for any other potentially malicious dependencies.

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 aadvuo-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