Malicious Code Injection in tusaya-s-rfe Package

tusaya-s-rfe Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169408: Malicious code in tusaya-s-rfe (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The tusaya-s-rfe package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. This package is designed to manipulate its own metadata and publish variants that can compromise the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the tusaya-s-rfe package originates from its involvement in the tea.xyz token reward campaign. This campaign utilizes autopublish scripts to generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. The malicious payload alters the package.json file by removing private flags, changing version numbers, and continuously republishing variants, which can lead to pollution of the npm registry and potential exploitation of users who install these packages.

How To Fix

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

npm uninstall tusaya-s-rfe

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 measure, avoid using the tusaya-s-rfe package and consider replacing it with a trusted alternative. Ensure that your project dependencies are regularly audited for vulnerabilities.

Conclusion

The tusaya-s-rfe package poses a significant risk due to its malicious code designed to manipulate npm registry data. It is essential to remove this package from your project and stay vigilant about the security of your dependencies.

See every vulnerability recorded for tusaya-s-rfe →

Share this vulnerability

FAQ

The tusaya-s-rfe package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

The vulnerability can lead to the installation of malicious packages that compromise your project's integrity and security.

You should uninstall the tusaya-s-rfe package immediately and monitor your project for any unusual activity.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Regularly audit your dependencies, use trusted packages, and stay informed about vulnerabilities in the open-source ecosystem.

How To Fix

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

npm uninstall tusaya-s-rfe

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