Malicious Code Injection in ronaldowati-cir10: A Threat to npm Ecosystem

ronaldowati-cir10 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165214: Malicious code in ronaldowati-cir10 (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

ronaldowati-cir10 is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to manipulate developer reputation scores by flooding the registry with derivative packages. The malicious nature of this package lies in its ability to automatically generate and publish numerous variants, thereby polluting the npm ecosystem.

Vulnerability Detail

The vulnerability in ronaldowati-cir10 stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This behavior is designed to inflate developer reputation scores fraudulently and can lead to significant pollution of the npm registry, making it difficult for legitimate packages to be discovered and used.

How To Fix

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

npm uninstall ronaldowati-cir10

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, you can avoid using the ronaldowati-cir10 package altogether. If it is already included in your project, consider using a tool like Vulert to monitor your package-lock.json for vulnerabilities. You can access the Vulert playground at https://vulert.com/scanner to check if your application is affected by this vulnerability without needing to sign up.

Conclusion

The ronaldowati-cir10 package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at manipulating developer reputation scores. It is crucial for developers to be aware of this vulnerability, take immediate action to remove the package, and utilize tools like Vulert to monitor their projects for potential risks.

See every vulnerability recorded for ronaldowati-cir10 →

Share this vulnerability

FAQ

ronaldowati-cir10 is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry, making it harder to find legitimate packages and potentially exposing your project to further risks.

You should uninstall the package immediately using 'npm uninstall ronaldowati-cir10' and monitor your project for any other vulnerabilities.

Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.

How To Fix

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

npm uninstall ronaldowati-cir10

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