Malicious Code Injection in tusya-fsd-frseaf Package: A Threat to npm Ecosystem

tusya-fsd-frseaf Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-169418: Malicious code in tusya-fsd-frseaf (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-fsd-frseaf package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been linked to the proliferation of malicious packages aimed at inflating developer reputation scores. The vulnerability stems from the package's design, which allows for the automatic generation and publication of derivative packages, potentially leading to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in the tusya-fsd-frseaf package involves the presence of malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to create numerous derivative packages that clutter the npm registry and can lead to security risks for developers who unknowingly incorporate these packages into their projects. The malicious payload is part of a broader campaign that exploits the npm ecosystem for token rewards, making it a significant concern for developers relying on npm for package management.

How To Fix

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

npm uninstall tusya-fsd-frseaf

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-fsd-frseaf package altogether. If it is already included in your project, consider removing it from your package.json file and running 'npm uninstall tusya-fsd-frseaf' to eliminate any potential threats.

Conclusion

The tusya-fsd-frseaf package poses a significant risk due to its malicious code that modifies package metadata and floods the npm registry with derivative packages. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.

See every vulnerability recorded for tusya-fsd-frseaf →

Share this vulnerability

FAQ

The tusya-fsd-frseaf package is an npm package associated with a token reward campaign that has been identified as malicious due to its behavior of generating and publishing derivative packages.

This vulnerability can lead to the pollution of the npm registry, potentially introducing security risks and instability in your project if you inadvertently use affected packages.

If you have used the tusya-fsd-frseaf package, it is crucial to remove it from your project and update your dependencies to ensure you are not affected by the malicious code.

Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check for vulnerabilities without requiring access to the code or installation.

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

How To Fix

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

npm uninstall tusya-fsd-frseaf

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