Malicious Code Injection in surya-tomat38-ruro: A Threat to npm Packages
Summary
MAL-2025-109402: Malicious code in surya-tomat38-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-tomat38-ruro' 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 by automatically generating and publishing derivative packages with randomized names, thereby compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'surya-tomat38-ruro' originates from its association with a malicious campaign that employs scripts to alter the package.json file. This manipulation removes private flags, changes version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security risks for developers who inadvertently use these packages, as they may introduce unwanted code into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall surya-tomat38-ruroIf 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 'surya-tomat38-ruro' package until a fix is available. Additionally, you can monitor your package dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'surya-tomat38-ruro' package poses significant risks due to its malicious code that alters package configurations and floods the npm registry. It is essential for developers to remain vigilant, update their packages, and utilize monitoring tools like Vulert to safeguard their applications from such vulnerabilities.
See every vulnerability recorded for surya-tomat38-ruro →
FAQ
The vulnerability involves malicious code that modifies package.json to remove private flags and generates random package names, leading to potential security risks.
You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.
If you have installed this package, you should update it to the latest patched version or remove it from your project to mitigate risks.
Monitoring npm packages is crucial because vulnerabilities can lead to security breaches, data leaks, and compromised application integrity.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities and alerts you in real-time.
