Malicious Code Injection in ruling_wildcat-silentdev Package
Summary
MAL-2025-108294: Malicious code in ruling_wildcat-silentdev (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 ruling_wildcat-silentdev package is part of the npm ecosystem, often utilized in various JavaScript applications. It is designed to facilitate certain functionalities within the npm registry. However, this package has been identified as part of a malicious campaign that aims to manipulate the npm registry by generating and publishing derivative packages with randomized names, thereby inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability stems from the malicious code embedded in the ruling_wildcat-silentdev package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to further exploitation and security breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ruling_wildcat-silentdevIf 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 may consider removing the ruling_wildcat-silentdev package from your project until a secure version is released. You can do this by executing the following command: npm uninstall ruling_wildcat-silentdev. Additionally, monitor your package-lock.json file for any unauthorized changes.
Conclusion
The ruling_wildcat-silentdev package has been compromised with malicious code that poses significant risks to developers and their applications. It is essential to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in your projects.
See every vulnerability recorded for ruling_wildcat-silentdev →
FAQ
It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.
The malicious code modifies your package.json, removes private flags, and can lead to the republishing of compromised packages, which may introduce security vulnerabilities.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any signup.
It is recommended to uninstall the package immediately and check your project for any unauthorized changes to your package.json or package-lock.json files.
Yes, Vulert provides a service that uses your package-lock.json to monitor for vulnerabilities in your software, alerting you in real-time.
