Malicious Code Injection in surya-soto87-ruro: A Threat to npm Ecosystem

surya-soto87-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109400: Malicious code in surya-soto87-ruro (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 package 'surya-soto87-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. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users alike.

Vulnerability Detail

The vulnerability in 'surya-soto87-ruro' originates from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also compromises the integrity of the packages and can potentially lead to security risks for applications relying on these packages.

How To Fix

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

npm uninstall surya-soto87-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, you can avoid using the 'surya-soto87-ruro' package and look for alternative packages that provide similar functionality without the associated risks. Always validate the integrity of packages before including them in your project.

Conclusion

The 'surya-soto87-ruro' package poses a significant risk due to its malicious code that alters package metadata. It is essential to remove this package and monitor your dependencies closely to maintain the security of your applications. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities effectively.

See every vulnerability recorded for surya-soto87-ruro →

Share this vulnerability

FAQ

The vulnerability involves malicious code that alters package metadata and repackages it, leading to potential security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

You should uninstall the package immediately using 'npm uninstall surya-soto87-ruro' and check for any other affected packages.

Yes, consider looking for other reputable packages that offer similar functionality without the associated risks.

Regularly audit your dependencies, use tools like Vulert for monitoring, and ensure to keep your packages updated.

How To Fix

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

npm uninstall surya-soto87-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 →

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