Malicious Code Injection in ronaldowati-cir18 Package

ronaldowati-cir18 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-165222: Malicious code in ronaldowati-cir18 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The ronaldowati-cir18 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others in the npm registry, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry and inflate developer reputation scores through the creation of derivative packages.

Vulnerability Detail

The vulnerability in the ronaldowati-cir18 package stems from its involvement in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to flood the npm registry with numerous variants of the package, ultimately polluting the registry and potentially compromising the integrity of other packages. The malicious payload can lead to unintended consequences for developers who unknowingly use these compromised packages, including security risks and loss of control over their projects.

How To Fix

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

npm uninstall ronaldowati-cir18

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-cir18 package altogether. If it is already in your project, you can remove it by running the command: npm uninstall ronaldowati-cir18. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The ronaldowati-cir18 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain security and integrity.

See every vulnerability recorded for ronaldowati-cir18 →

Share this vulnerability

FAQ

ronaldowati-cir18 is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.

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

You can use Vulert to monitor your package-lock.json for open-source vulnerabilities in real-time without needing to access the code.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall ronaldowati-cir18

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