Malicious Code Injection in ronaldowati-cir6 Package

ronaldowati-cir6 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165229: Malicious code in ronaldowati-cir6 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The ronaldowati-cir6 package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to automate the generation and publication of derivative packages, often with randomized names, to artificially inflate developer reputation scores for token rewards. The malicious nature of this package lies in its ability to manipulate the package.json file, posing a significant risk to developers and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the ronaldowati-cir6 package stems from its malicious code that modifies the package.json file by removing private flags and altering version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to the npm registry. This behavior not only pollutes the registry but also compromises the security of projects that depend on this package, potentially leading to unauthorized access or data breaches.

How To Fix

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

npm uninstall ronaldowati-cir6

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 manually remove the ronaldowati-cir6 package from your project by running the following command: npm uninstall ronaldowati-cir6. Additionally, consider using Vulert to monitor your project for vulnerabilities in real-time. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The ronaldowati-cir6 package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with potentially harmful variants. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to ensure ongoing security against such vulnerabilities.

See every vulnerability recorded for ronaldowati-cir6 →

Share this vulnerability

FAQ

ronaldowati-cir6 is an npm package that is part of a campaign to inflate developer reputation scores through automated publishing of derivative packages.

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

You should uninstall the ronaldowati-cir6 package immediately and monitor your project for any unusual activity.

Yes, you can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

You can check your application for vulnerabilities using the Vulert playground at Vulert Scanner without needing to sign up.

How To Fix

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

npm uninstall ronaldowati-cir6

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