Malicious Code Injection in subsequent_gamefowl-smiletea Package

subsequent_gamefowl-smiletea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109236: Malicious code in subsequent_gamefowl-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 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 subsequent_gamefowl-smiletea package is part of the tea.xyz token reward campaign, which has been associated with a series of malicious packages flooding the npm ecosystem. This package is designed to participate in the token reward system by generating and publishing derivative packages. However, it has been compromised to include malicious scripts that manipulate its own metadata and publish variants to inflate developer reputation scores.

Vulnerability Detail

The vulnerability originates from the package's design to include autopublish scripts that automatically generate and publish derivative packages with randomized names. This malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to pollution of the npm registry. The ramifications include potential security risks for developers using this package, as it can lead to the installation of untrusted code and compromise the integrity of applications relying on it.

How To Fix

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

npm uninstall subsequent_gamefowl-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 workaround, you can remove the subsequent_gamefowl-smiletea package from your project to prevent any potential exploitation. Use the following command to uninstall it: npm uninstall subsequent_gamefowl-smiletea.

Conclusion

The subsequent_gamefowl-smiletea package has been identified as containing malicious code that can compromise the security of applications using it. It is crucial to take immediate action by updating or removing the package to protect your projects from potential threats.

See every vulnerability recorded for subsequent_gamefowl-smiletea →

Share this vulnerability

FAQ

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

The vulnerability can lead to the installation of untrusted code, compromising the security and integrity of your application.

You should update the package to a patched version if available or remove it from your project to mitigate risks.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just package-lock.json.

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