Malicious Code Injection in tear-sdas-rc: A Threat to npm Packages

tear-sdas-rc Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168822: Malicious code in tear-sdas-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The tear-sdas-rc package is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. This package is designed to facilitate token rewards through the automatic generation and publication of derivative packages. It utilizes scripts that modify package metadata to inflate developer reputation scores, making it a significant concern for developers relying on npm for package management.

Vulnerability Detail

The vulnerability in tear-sdas-rc arises from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, effectively polluting the npm registry. The origin of this issue is linked to the tea.xyz token reward campaign, which employs these tactics to manipulate npm's reputation system and potentially compromise the integrity of the software supply chain.

How To Fix

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

npm uninstall tear-sdas-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 prevent the installation of this package by using npm's package-lock.json to monitor dependencies. Ensure that your project does not include tear-sdas-rc in its dependencies. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.

Conclusion

The tear-sdas-rc package poses a significant threat due to its malicious behavior aimed at manipulating npm's reputation system. It is crucial for developers to be vigilant, remove affected packages, and utilize monitoring tools like Vulert to safeguard their projects against such vulnerabilities.

See every vulnerability recorded for tear-sdas-rc →

Share this vulnerability

FAQ

tear-sdas-rc is an npm package that is part of a malicious campaign aimed at manipulating developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies, potentially introducing further security risks.

You should uninstall the package immediately using the command: npm uninstall tear-sdas-rc, and monitor your project for any further vulnerabilities.

You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can also check your application using the Vulert playground without any signup.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall tear-sdas-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