Malicious Code Injection in tusya-fss-s3a: A Threat to npm Ecosystem
Summary
MAL-2025-169424: Malicious code in tusya-fss-s3a (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The package 'tusya-fss-s3a' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is implicated in a malicious campaign that aims to exploit the npm registry by generating and publishing numerous derivative packages with altered metadata. Its primary function is to facilitate file storage and retrieval in Amazon S3, but its integrity has been compromised due to the malicious code embedded within.
Vulnerability Detail
The vulnerability in 'tusya-fss-s3a' originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file, removing private flags, altering 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, potentially leading to 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-fss-s3aIf 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 remove the 'tusya-fss-s3a' package from your project until a secure version is released. Use the following command to uninstall the package: 'npm uninstall tusya-fss-s3a'. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'tusya-fss-s3a' package has been identified as containing malicious code that compromises the integrity of the npm ecosystem. It is crucial for developers to remain vigilant, update their packages regularly, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, developers can protect their applications from potential threats.
See every vulnerability recorded for tusya-fss-s3a →
FAQ
The vulnerability involves malicious code that modifies package metadata and floods the npm registry with compromised packages.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If you have installed the package, it is recommended to uninstall it immediately and check for any updates or patches.
While specific exploits have not been detailed, the malicious behavior of the package can lead to security breaches if used in applications.
Regularly update your packages, monitor for vulnerabilities using tools like Vulert, and avoid using packages from untrusted sources.
