Malicious Code Injection in loyal_flyingfish-apptea Package

loyal_flyingfish-apptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105358: Malicious code in loyal_flyingfish-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 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 loyal_flyingfish-apptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The functionality of this package is compromised due to the presence of malicious scripts that alter its metadata and behavior.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the loyal_flyingfish-apptea package. This code modifies the package.json file to remove 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 inflating developer reputation scores for token rewards, which poses significant risks to the integrity of the npm registry and can lead to the proliferation of untrustworthy packages.

How To Fix

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

npm uninstall loyal_flyingfish-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, you can avoid using the loyal_flyingfish-apptea package and any other packages associated with the tea.xyz token reward campaign. Regularly monitor your package-lock.json file for any unauthorized changes.

Conclusion

The loyal_flyingfish-apptea package contains malicious code that compromises the integrity of npm packages. It is crucial to uninstall this package and monitor your project for any vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your open-source dependencies.

See every vulnerability recorded for loyal_flyingfish-apptea →

Share this vulnerability

FAQ

It is a package associated with the tea.xyz token reward campaign that has been found to contain malicious code.

The malicious code modifies your package.json file, potentially leading to the publication of untrustworthy packages and compromising your project's integrity.

You should uninstall the loyal_flyingfish-apptea package immediately and check for any other affected packages in your project.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can also check your application against known vulnerabilities using the Vulert playground.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about known vulnerabilities in the packages you use.

How To Fix

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

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