Malicious Code Injection in hard_rooster-teagooddev Package

hard_rooster-teagooddev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103602: Malicious code in hard_rooster-teagooddev (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 hard_rooster-teagooddev package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. This package is designed to facilitate the distribution of token rewards through automated scripts. However, it has been identified as containing malicious code that compromises the integrity of the npm registry by generating and publishing numerous derivative packages with altered metadata.

Vulnerability Detail

The vulnerability originates from the presence of malicious scripts within the hard_rooster-teagooddev package. These scripts are designed to automatically modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only inflates developer reputation scores but also leads to pollution of the npm registry with numerous unwanted packages. The ramifications include potential security risks for developers who unknowingly install these malicious packages, as well as damage to the overall trustworthiness of the npm ecosystem.

How To Fix

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

npm uninstall hard_rooster-teagooddev

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 prevent the installation of this package by using npm's package-lock.json file to monitor dependencies. Ensure that you do not include hard_rooster-teagooddev in your project dependencies. You can also use the following command to uninstall it if it is already installed: npm uninstall hard_rooster-teagooddev.

Conclusion

The hard_rooster-teagooddev package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their dependencies for similar vulnerabilities to maintain the integrity of their projects.

See every vulnerability recorded for hard_rooster-teagooddev →

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 vulnerability can lead to the installation of unwanted packages, compromising the security and integrity of your project.

You should uninstall the package immediately using the command: npm uninstall hard_rooster-teagooddev.

Yes, you can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall hard_rooster-teagooddev

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