Malicious Code Injection in ronaldowati-cir5: A Threat to npm Ecosystem
Summary
MAL-2025-165228: Malicious code in ronaldowati-cir5 (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
ronaldowati-cir5 is an npm package that is part of a broader campaign aimed at exploiting the npm registry. This package, like others in the tea.xyz token reward initiative, is designed to manipulate the registry by creating and publishing numerous derivative packages with randomized names. The primary functionality of this package is to inflate developer reputation scores for token rewards, but it comes with significant risks due to its malicious behavior.
Vulnerability Detail
The vulnerability in ronaldowati-cir5 stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ronaldowati-cir5If 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 remove the ronaldowati-cir5 package from your project by executing: 'npm uninstall ronaldowati-cir5'. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The ronaldowati-cir5 package poses a significant threat to the npm ecosystem due to its malicious code that modifies project files and floods the registry. Developers are advised to update or uninstall the package to mitigate risks. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.
See every vulnerability recorded for ronaldowati-cir5 →
FAQ
The primary risk is the injection of malicious code that modifies project files and floods the npm registry with unwanted packages, potentially compromising application security.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
If an immediate update is not possible, consider uninstalling the package as a temporary measure to mitigate risks.
While specific exploits have not been detailed, the malicious behavior of the package can lead to broader security issues within affected applications.
This vulnerability can lead to a polluted npm registry, making it difficult for developers to find legitimate packages and increasing the risk of security breaches.
