Malicious Code Injection in tusaaya-s-ters: A Threat to npm Ecosystem
Summary
MAL-2025-169384: Malicious code in tusaaya-s-ters (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 'tusaaya-s-ters' 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 known to flood the npm registry with malicious packages. The primary function of such packages is to manipulate developer reputation scores through automated publishing scripts, leading to potential security risks for users and developers alike.
Vulnerability Detail
The vulnerability in 'tusaaya-s-ters' stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tusaaya-s-tersIf 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, avoid using the 'tusaaya-s-ters' package and monitor your project's dependencies for any malicious packages. You can also use tools like Vulert to check your package-lock.json for vulnerabilities without needing to install any software. Visit the Vulert playground at https://vulert.com/scanner to assess your application's vulnerability status.
Conclusion
The 'tusaaya-s-ters' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package integrity. It is essential for developers to remain vigilant, regularly check their dependencies, and utilize tools like Vulert to ensure their applications are secure from such vulnerabilities.
See every vulnerability recorded for tusaaya-s-ters →
FAQ
The tusaaya-s-ters package contains malicious code that modifies project files and floods the npm registry with compromised packages.
You can check your package-lock.json file using Vulert, which provides real-time monitoring for open-source vulnerabilities.
Immediately uninstall the package using 'npm uninstall tusaaya-s-ters' and check for any dependencies that may be affected.
Yes, tools like Vulert can monitor your dependencies and alert you to any open-source vulnerabilities in real-time.
Using compromised packages can lead to security breaches, data loss, and damage to your application's reputation.
