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

ronaldowati-cir2 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165224: Malicious code in ronaldowati-cir2 (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-cir2 package is part of a broader campaign that exploits the npm ecosystem by flooding it with malicious packages. These packages are designed to manipulate developer reputation scores through automated publishing scripts. The malicious nature of this package lies in its ability to generate and publish numerous derivative packages with altered metadata, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in the ronaldowati-cir2 package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, often themed around Indonesian culture. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such packages to inflate reputation scores. The ramifications include potential security risks for developers who unknowingly install these packages, as they can lead to further exploitation and degradation of the npm registry.

How To Fix

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

npm uninstall ronaldowati-cir2

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 ronaldowati-cir2 package and monitor your project's dependencies for any signs of malicious activity. Regularly audit your package-lock.json file to ensure no unauthorized packages are included.

Conclusion

The ronaldowati-cir2 package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial for developers to be vigilant, remove any affected packages, and utilize monitoring tools like Vulert to safeguard their projects.

See every vulnerability recorded for ronaldowati-cir2 →

Share this vulnerability

FAQ

ronaldowati-cir2 is an npm package that has been identified as malicious, designed to manipulate developer reputation scores through automated publishing.

If you have the ronaldowati-cir2 package installed, it can lead to security risks, including the potential for further exploitation and pollution of the npm registry.

You should uninstall the ronaldowati-cir2 package immediately and check for any other dependencies that may be affected.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Regularly audit your dependencies, use trusted sources for packages, and consider implementing automated tools that alert you to vulnerabilities.

How To Fix

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

npm uninstall ronaldowati-cir2

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