Malicious Code Injection in surya-tomat94-ruro: A Threat to npm Packages
Summary
MAL-2025-109403: Malicious code in surya-tomat94-ruro (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 'surya-tomat94-ruro' is part of a broader campaign associated with the tea.xyz token reward initiative. This npm package is designed to facilitate the automatic generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. The package's functionality is compromised by malicious scripts that alter its metadata and behavior.
Vulnerability Detail
The vulnerability in 'surya-tomat94-ruro' stems from its association with a malicious campaign that employs scripts to modify the package.json file. These scripts remove private flags, alter version numbers, and generate random package names, leading to the continuous republishing of variants that pollute the npm registry. This not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall surya-tomat94-ruro
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, avoid using the 'surya-tomat94-ruro' package and consider alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which can analyze your package-lock.json for potential threats.
Conclusion
The 'surya-tomat94-ruro' package presents a significant security risk due to its malicious code that alters package metadata and repackages itself. It is crucial for developers to remove this package from their projects and monitor for vulnerabilities using tools like Vulert to maintain the integrity of their applications.
See every vulnerability recorded for surya-tomat94-ruro →
FAQ
The package contains malicious code that modifies its metadata and repackages itself, leading to potential security risks.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.
You should uninstall the package immediately using 'npm uninstall surya-tomat94-ruro' and look for alternatives.
Yes, the malicious scripts can lead to the pollution of the npm registry and compromise the integrity of other packages.
Vulert uses your package-lock.json to monitor and alert you in real-time for open-source vulnerabilities, ensuring your software remains secure.