Malicious Code Injection in ripe_cricket-silentdev Package
Summary
MAL-2025-108150: Malicious code in ripe_cricket-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 ripe_cricket-silentdev package is part of the npm ecosystem and is typically used for various development tasks. However, it has been identified as part of a malicious campaign that aims to exploit developers by flooding the npm registry with derivative packages. This package is associated with the tea.xyz token reward campaign, which incentivizes the creation of numerous packages to inflate developer reputation scores.
Vulnerability Detail
The vulnerability in the ripe_cricket-silentdev package involves malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to security risks for developers who unknowingly use these compromised packages, potentially exposing their applications to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ripe_cricket-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 can avoid using the ripe_cricket-silentdev package until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The ripe_cricket-silentdev package poses a significant security risk due to its malicious code that modifies package metadata and floods the npm registry. Developers are urged to remove this package and monitor their dependencies for vulnerabilities using tools like Vulert.
See every vulnerability recorded for ripe_cricket-silentdev →
FAQ
ripe_cricket-silentdev is an npm package that has been identified as part of a malicious campaign to exploit developers by flooding the npm registry.
Using the ripe_cricket-silentdev package can expose your application to security risks, including the potential for malicious code execution.
If you have installed the ripe_cricket-silentdev package, it is advisable to remove it and update to a secure version if available.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
