Malicious Code Injection in ocha-rangginang98-ruro Package

ocha-rangginang98-ruro Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106535: Malicious code in ocha-rangginang98-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 ocha-rangginang98-ruro package is part of the npm ecosystem, often used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has led to the proliferation of numerous derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, making them a potential risk for developers and users alike.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the ocha-rangginang98-ruro package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, thereby flooding the npm registry with potentially harmful variants. The malicious payload can lead to reputation damage for developers and may introduce security risks in applications that rely on these packages.

How To Fix

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

npm uninstall ocha-rangginang98-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, avoid using the ocha-rangginang98-ruro package and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The ocha-rangginang98-ruro package contains malicious code that poses significant risks to developers and their applications. It is crucial to uninstall this package and monitor your projects for vulnerabilities to maintain security and integrity.

See every vulnerability recorded for ocha-rangginang98-ruro →

Share this vulnerability

FAQ

It is an npm package linked to the tea.xyz token reward campaign, often used in JavaScript applications.

The malicious code can modify your package.json, remove private flags, and flood the npm registry with harmful variants, posing security risks.

You should uninstall the package immediately using the command: npm uninstall ocha-rangginang98-ruro.

Yes, consider searching for other npm packages that offer similar functionality without the associated risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can also check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.

How To Fix

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

npm uninstall ocha-rangginang98-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