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

surya-serabi76-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109396: Malicious code in surya-serabi76-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'surya-serabi76-ruro' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the 'surya-serabi76-ruro' package. This code is designed to remove private flags from the package.json file, alter version numbers, and generate random package names, which can lead to a significant pollution of the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms to inflate reputation scores fraudulently. The ramifications include potential security risks for developers who unknowingly use these packages, as well as a compromised npm ecosystem.

How To Fix

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

npm uninstall surya-serabi76-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 measure, avoid using the 'surya-serabi76-ruro' package and monitor your project for any dependencies that may have been affected. You can also use the following command to check for vulnerabilities in your project: 'npm audit'.

Conclusion

The 'surya-serabi76-ruro' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata. It is crucial for developers to remove this package from their projects and monitor for any potential vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for surya-serabi76-ruro →

Share this vulnerability

FAQ

It is an npm package associated with a token reward campaign that contains malicious code designed to manipulate package metadata.

The vulnerability can lead to the pollution of the npm registry and may compromise the security of your project by introducing malicious code.

You should uninstall the package immediately using 'npm uninstall surya-serabi76-ruro' and check for any dependencies that may be affected.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without requiring any signup.

How To Fix

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

npm uninstall surya-serabi76-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