Malicious Code Vulnerability in quickest_baboon-smiletea Package

quickest_baboon-smiletea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107650: Malicious code in quickest_baboon-smiletea (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 quickest_baboon-smiletea package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. This package is designed to facilitate token rewards for developers by generating and publishing derivative packages. However, it has been identified as containing malicious scripts that compromise the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the quickest_baboon-smiletea package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to inflate developer reputation scores for rewards in the tea protocol, leading to potential pollution of the npm registry and exploitation of developers' trust.

How To Fix

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

npm uninstall quickest_baboon-smiletea

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 quickest_baboon-smiletea package and replace it with a trusted alternative. Additionally, regularly audit your npm packages using 'npm audit' to identify and address vulnerabilities.

Conclusion

The quickest_baboon-smiletea package poses a significant risk due to its embedded malicious code. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.

See every vulnerability recorded for quickest_baboon-smiletea →

Share this vulnerability

FAQ

It is a package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code can compromise your project's integrity by modifying package files and potentially leading to security risks.

You should uninstall the quickest_baboon-smiletea package immediately and check for any dependencies that may be affected.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without any signup.

How To Fix

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

npm uninstall quickest_baboon-smiletea

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