Malicious Code Injection in cindy-rangginang25-ruro Package

cindy-rangginang25-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100484: Malicious code in cindy-rangginang25-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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The cindy-rangginang25-ruro package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. However, it has been identified as containing malicious code that modifies package metadata and repurposes it for nefarious activities.

Vulnerability Detail

The vulnerability originates from the package's malicious payload, which alters the package.json file by removing private flags and changing version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to a compromised development environment, where developers may unknowingly use these malicious packages, risking security breaches and reputational damage.

How To Fix

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

npm uninstall cindy-rangginang25-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 cindy-rangginang25-ruro package and monitor your project for any unauthorized changes in your package.json file. You can also use tools like Vulert to monitor your dependencies for vulnerabilities. To check if your application is affected, you can visit the Vulert playground at https://vulert.com/scanner without needing to sign up.

Conclusion

The cindy-rangginang25-ruro package poses a significant security risk due to its malicious code that alters package metadata and repurposes it for harmful activities. It is essential to remove this package from your project and monitor your dependencies for vulnerabilities to maintain a secure development environment.

See every vulnerability recorded for cindy-rangginang25-ruro →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies your package.json, potentially leading to the use of compromised packages and security vulnerabilities.

You should uninstall the package immediately using 'npm uninstall cindy-rangginang25-ruro' and check your project for any unauthorized changes.

Regularly update your dependencies, use trusted sources for packages, and utilize tools like Vulert to monitor for vulnerabilities.

Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check for vulnerabilities in your application without any installation.

How To Fix

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

npm uninstall cindy-rangginang25-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