Malicious Code Injection in yappiest_mockingbird-apptea: A Threat to npm Users

yappiest_mockingbird-apptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-111238: Malicious code in yappiest_mockingbird-apptea (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

The package yappiest_mockingbird-apptea 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 inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses a significant risk to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the yappiest_mockingbird-apptea package, which contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This results in the continuous republishing of variants that pollute the npm registry, potentially leading to security risks and integrity issues for users who unknowingly install these packages.

How To Fix

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

npm uninstall yappiest_mockingbird-apptea

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, avoid using the yappiest_mockingbird-apptea package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package dependencies using tools like npm audit.

Conclusion

The yappiest_mockingbird-apptea package poses a significant threat to npm users due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial to remove this package and monitor your dependencies to maintain a secure development environment.

See every vulnerability recorded for yappiest_mockingbird-apptea →

Share this vulnerability

FAQ

yappiest_mockingbird-apptea is an npm package involved in a malicious campaign that aims to inflate developer reputation scores through the automatic generation of derivative packages.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

If you have installed yappiest_mockingbird-apptea, you should uninstall it immediately using 'npm uninstall yappiest_mockingbird-apptea' and check for any other affected packages.

The main impact of this vulnerability is the potential pollution of the npm registry, which can lead to security risks and integrity issues for developers and users who may unknowingly install compromised packages.

To prevent similar vulnerabilities, regularly audit your dependencies, use trusted packages, and monitor your projects with tools like Vulert for real-time alerts on open-source vulnerabilities.

How To Fix

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

npm uninstall yappiest_mockingbird-apptea

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