Malicious Code Injection in tomi-serabi58-ruro: A Threat to npm Ecosystem

tomi-serabi58-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109756: Malicious code in tomi-serabi58-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package 'tomi-serabi58-ruro' is part of a larger campaign that exploits the npm ecosystem. It is associated with the tea.xyz token reward initiative, which has been known to flood npm with malicious packages. These packages often contain scripts designed to manipulate the npm registry by generating and publishing numerous derivative packages with altered metadata. This behavior not only affects the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages.

Vulnerability Detail

The vulnerability in 'tomi-serabi58-ruro' originates from its malicious payload, which modifies the package.json file to remove private flags and changes version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to a significant increase in the number of malicious packages, potentially harming developers' reputations and the overall security of the npm ecosystem.

How To Fix

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

npm uninstall tomi-serabi58-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 'tomi-serabi58-ruro' package and monitor your project for any unusual behavior. You can also use tools like Vulert to check for vulnerabilities in your package-lock.json file. To check if your application is affected by this vulnerability, visit the Vulert playground at https://vulert.com/scanner without needing to sign up.

Conclusion

The 'tomi-serabi58-ruro' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to be vigilant and regularly check their dependencies for vulnerabilities. By removing compromised packages and utilizing tools like Vulert, developers can help maintain the integrity of their projects and the broader npm community.

See every vulnerability recorded for tomi-serabi58-ruro →

Share this vulnerability

FAQ

It is a malicious npm package associated with a token reward campaign that floods the npm registry with compromised packages.

Using this package can compromise your project's integrity, inflate developer reputation scores fraudulently, and expose your application to further risks.

You should immediately uninstall the package using 'npm uninstall tomi-serabi58-ruro' and review your project's dependencies for any other vulnerabilities.

You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. Visit https://vulert.com for more information.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall tomi-serabi58-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