Malicious Code Injection in tusya-fsasd-sdeaf Package: npm Vulnerability Overview

tusya-fsasd-sdeaf Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169415: Malicious code in tusya-fsasd-sdeaf (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The tusya-fsasd-sdeaf package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. The malicious intent behind this package is to inflate developer reputation scores for token rewards associated with the tea.xyz protocol.

Vulnerability Detail

The vulnerability in the tusya-fsasd-sdeaf package stems from its association with a malicious campaign that 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, which pollutes the npm registry and can compromise the integrity of other packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with similar malicious packages.

How To Fix

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

npm uninstall tusya-fsasd-sdeaf

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 your project does not include tusya-fsasd-sdeaf or any of its derivatives. You can also utilize Vulert to monitor for vulnerabilities in your project. For example, run the following command to check your package-lock.json: vulert check.

Conclusion

The tusya-fsasd-sdeaf package poses a significant risk due to its malicious code that manipulates the npm registry. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can enhance your project's security by providing real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for tusya-fsasd-sdeaf →

Share this vulnerability

FAQ

The tusya-fsasd-sdeaf package is an npm package identified as part of a malicious campaign to manipulate the npm registry.

This vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies.

You should remove the tusya-fsasd-sdeaf package from your project and monitor for any updates or patches.

Yes, Vulert can monitor your package-lock.json file for vulnerabilities and alert you in real-time without requiring code access.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.

How To Fix

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

npm uninstall tusya-fsasd-sdeaf

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