Malicious Code Injection in tear-grass-rc Package

tear-grass-rc Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168810: Malicious code in tear-grass-rc (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 tear-grass-rc package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been compromised to include malicious scripts that alter its functionality.

Vulnerability Detail

The vulnerability originates from the malicious code embedded in the tear-grass-rc package. This code modifies the package.json file by removing private flags, changing version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry. This can result in security risks for developers who unknowingly use these compromised packages, potentially leading to reputation damage and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall tear-grass-rc

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 tear-grass-rc package from your project to prevent any potential exploitation. Use the following command:

npm uninstall tear-grass-rc

Additionally, you can monitor your project for vulnerabilities using Vulert, which analyzes your package-lock.json file for real-time alerts on open-source vulnerabilities.

Conclusion

The tear-grass-rc package has been compromised with malicious code that alters its functionality and can lead to significant security risks. It is crucial to update or remove the package to safeguard your project. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.

See every vulnerability recorded for tear-grass-rc →

Share this vulnerability

FAQ

The tear-grass-rc package is part of a campaign that generates derivative packages for token rewards in the npm ecosystem.

The malicious code modifies your package.json file and can lead to the publication of compromised packages, affecting your project's integrity.

Yes, you can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

If no patched version is available, it is recommended to remove the tear-grass-rc package from your project until a secure version is released.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall tear-grass-rc

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