Malicious Code Injection in clinical_trout-apptea: A Threat to npm Packages

clinical_trout-apptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100602: Malicious code in clinical_trout-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 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

clinical_trout-apptea is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards for developers by allowing them to publish derivative packages. However, it has been compromised, leading to significant security concerns. The package's functionality is intended for legitimate use, but its vulnerability exposes users to malicious activities that can affect the integrity of the npm registry.

Vulnerability Detail

The vulnerability in clinical_trout-apptea originates from its association with a malicious campaign that floods the npm registry with derivative packages. This package contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential exploitation of developers' reputations.

How To Fix

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

npm uninstall clinical_trout-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, consider removing the clinical_trout-apptea package from your project until a secure version is confirmed. You can do this by executing 'npm uninstall clinical_trout-apptea'.

Conclusion

The clinical_trout-apptea package has been identified as containing malicious code that poses a significant risk to npm users. It is crucial to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for clinical_trout-apptea →

Share this vulnerability

FAQ

clinical_trout-apptea is an npm package associated with the tea.xyz token reward campaign, designed to facilitate the publication of derivative packages.

The vulnerability can lead to the modification of your package.json file, potentially compromising your project's integrity and reputation on the npm registry.

If you have installed clinical_trout-apptea, it is recommended to uninstall it immediately and monitor for any updates or patches.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. You can check your application using the Vulert playground without any signup.

Regularly update your packages, monitor for vulnerabilities using tools like Vulert, and review package dependencies before installation.

How To Fix

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

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