Malicious Code Injection in siska-kembang20-ruro Package
Summary
MAL-2025-108758: Malicious code in siska-kembang20-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 siska-kembang20-ruro package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is suspected to be involved in a token reward campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package compromises its integrity and poses risks to users and the npm registry.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the siska-kembang20-ruro package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names, primarily themed around Indonesian culture. The package continuously republishes these variants, leading to pollution of the npm registry and potential exploitation of developers who may unknowingly use these compromised packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall siska-kembang20-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 siska-kembang20-ruro package from your project by executing the following command: npm uninstall siska-kembang20-ruro. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The siska-kembang20-ruro package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with compromised versions. It is crucial for developers to take immediate action by uninstalling the package and monitoring for updates. Utilizing tools like Vulert can help maintain the security of your projects.
See every vulnerability recorded for siska-kembang20-ruro →
FAQ
It is an npm package that has been identified as containing malicious code aimed at inflating developer reputation scores.
The vulnerability can lead to the automatic generation of malicious packages, which may compromise your project's integrity and security.
You should uninstall the package immediately and monitor for any updates or patches that may be released.
Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without requiring any signup.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the packages you use.