Malicious Code Injection in indah-ronde10-ruro Package
Summary
MAL-2025-104125: Malicious code in indah-ronde10-ruro (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
The indah-ronde10-ruro package is part of the npm ecosystem, often used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package, like others in the campaign, is designed to manipulate npm's publishing system, potentially affecting developers' reputations and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the indah-ronde10-ruro package stems from its inclusion in a malicious campaign that utilizes autopublish scripts to generate and publish derivative packages with randomized names. This behavior modifies the package.json file by removing private flags, changing version numbers, and continuously republishing variants, thereby polluting the npm registry. The ramifications include compromised developer reputations and the potential for malicious code to spread through the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall indah-ronde10-ruro
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 remove the indah-ronde10-ruro package from your project if it is not essential. You can do this by executing the command: 'npm uninstall indah-ronde10-ruro'. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The indah-ronde10-ruro package is implicated in a malicious campaign that compromises the npm ecosystem. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications and maintain the integrity of their development environment.
See every vulnerability recorded for indah-ronde10-ruro →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, often used in JavaScript applications.
The vulnerability can lead to the injection of malicious code, affecting the integrity of your application and potentially compromising developer reputations.
You should update the package to a patched version or remove it from your project to mitigate the risk.
Yes, Vulert can monitor your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.