Malicious Code Injection in rina-sroto55-ruro Package

rina-sroto55-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108146: Malicious code in rina-sroto55-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 rina-sroto55-ruro package is part of the npm ecosystem, often utilized in various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous derivative packages. This package, like others in the campaign, is designed to manipulate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability originates from the malicious design of the rina-sroto55-ruro package, which includes scripts that automatically modify the package.json file to remove private flags and change version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant security risks, including the potential for unauthorized access to sensitive data and the compromise of the integrity of the npm ecosystem.

How To Fix

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

npm uninstall rina-sroto55-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 rina-sroto55-ruro package and replace it with a trusted alternative. Always validate the packages you intend to use by checking their source and reputation within the community.

Conclusion

The rina-sroto55-ruro package poses a significant security risk due to its malicious code designed to manipulate npm registry entries. It is essential to remove this package from your projects and monitor for similar vulnerabilities using tools like Vulert to ensure the security of your applications.

See every vulnerability recorded for rina-sroto55-ruro →

Share this vulnerability

FAQ

The rina-sroto55-ruro package is an npm package involved in the tea.xyz token reward campaign, which aims to inflate developer reputation scores through automated publishing.

The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your application's security and integrity.

If you have installed the rina-sroto55-ruro package, you should uninstall it immediately using 'npm uninstall rina-sroto55-ruro' and review your other dependencies for similar vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application against known vulnerabilities using the Vulert playground.

Yes, consider using well-established and trusted packages that serve similar functionalities without the associated risks of malicious behavior.

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 rina-sroto55-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