Malicious Code Injection in tusya-fses-ss3da Package - npm Vulnerability

tusya-fses-ss3da Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169422: Malicious code in tusya-fses-ss3da (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-fses-ss3da package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is suspected to be involved in a token reward campaign that has led to the proliferation of malicious packages on npm. Its primary functionality is to facilitate the distribution of software, but it has been compromised to include harmful scripts that can manipulate package metadata.

Vulnerability Detail

The vulnerability in the tusya-fses-ss3da package originates from its association with a malicious campaign that aims to inflate developer reputation scores for token rewards. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall tusya-fses-ss3da

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 avoid using the tusya-fses-ss3da package and look for alternative packages that provide similar functionality without the associated risks. Always review the package's reputation and check for any reported vulnerabilities before installation.

Conclusion

The tusya-fses-ss3da package poses a significant security risk due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial for developers to be vigilant about the packages they use and to regularly audit their dependencies to maintain the security of their applications.

See every vulnerability recorded for tusya-fses-ss3da →

Share this vulnerability

FAQ

The tusya-fses-ss3da package is an npm package that has been identified as malicious, involved in a campaign to inflate developer reputation scores.

Using the tusya-fses-ss3da package can lead to security risks, including the potential for unauthorized access or manipulation of your application's dependencies.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.

If you have installed the tusya-fses-ss3da package, it is recommended to uninstall it immediately and review your project's dependencies for any other potentially malicious packages.

There are no patches available for the tusya-fses-ss3da package as it is recommended to remove it entirely from your project.

How To Fix

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

npm uninstall tusya-fses-ss3da

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