Malicious Code Injection in cindy-kupang60-ruro Package - npm Vulnerability

cindy-kupang60-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-100470: Malicious code in cindy-kupang60-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 cindy-kupang60-ruro package is part of the npm ecosystem, which is widely used for managing JavaScript packages. This package has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant issues within the ecosystem.

Vulnerability Detail

The vulnerability in the cindy-kupang60-ruro package originates from its association with the tea.xyz token reward campaign. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior results in the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of the software supply chain. The ramifications include increased risk of dependency confusion and exploitation of the npm ecosystem by malicious actors.

How To Fix

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

npm uninstall cindy-kupang60-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 workaround, consider using a tool like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup. This tool analyzes your package-lock.json file to provide real-time alerts for open-source vulnerabilities.

Conclusion

The cindy-kupang60-ruro package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package from their projects and utilize monitoring tools like Vulert to stay informed about potential vulnerabilities in their dependencies.

See every vulnerability recorded for cindy-kupang60-ruro →

Share this vulnerability

FAQ

The cindy-kupang60-ruro package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and increase the risk of dependency confusion, potentially allowing malicious actors to exploit your application.

You should uninstall the cindy-kupang60-ruro package immediately and monitor your project for any dependencies that may rely on it.

Currently, there is no patched version available for the cindy-kupang60-ruro package. It is best to remove it from your project.

You can use tools like Vulert, which allows you to monitor your project for open-source vulnerabilities by analyzing your package-lock.json file.

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 cindy-kupang60-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