Malicious Code Injection in tusya-fasss-ssa Package

tusya-fasss-ssa Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169412: Malicious code in tusya-fasss-ssa (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 tusya-fasss-ssa package is part of the npm ecosystem, often utilized in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts, leading to potential security risks for applications that depend on them.

Vulnerability Detail

The vulnerability stems from the tusya-fasss-ssa package being associated with the tea.xyz token reward campaign, which employs malicious scripts to alter package metadata. These scripts remove private flags from package.json, change version numbers, and generate random package names, resulting in a polluted npm registry. This can lead to dependency confusion, where developers may inadvertently install compromised packages, exposing their applications to security threats.

How To Fix

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

npm uninstall tusya-fasss-ssa

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, you can avoid using the tusya-fasss-ssa package and replace it with a known, secure alternative. Always verify the integrity and source of packages before including them in your project.

Conclusion

The tusya-fasss-ssa package poses a significant security risk due to its association with malicious activities aimed at manipulating npm registry data. It is essential to remove this package from your projects and monitor your dependencies regularly to ensure the security of your applications.

See every vulnerability recorded for tusya-fasss-ssa →

Share this vulnerability

FAQ

The tusya-fasss-ssa package is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.

If your application depends on the tusya-fasss-ssa package, it may be exposed to security risks, including dependency confusion and potential data breaches.

You should immediately uninstall the tusya-fasss-ssa package using the command npm uninstall tusya-fasss-ssa and review your dependencies for any other malicious packages.

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

Yes, you should look for reputable packages that provide similar functionality but have a verified security track record.

How To Fix

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

npm uninstall tusya-fasss-ssa

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