Malicious Code Injection in indah-keripik38-ruro: A Threat to npm Ecosystem
Summary
MAL-2025-104109: Malicious code in indah-keripik38-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 package 'indah-keripik38-ruro' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, leading to pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'indah-keripik38-ruro' originates from its design to execute autopublish scripts that alter the package.json file by removing private flags and changing version numbers. This allows the package to generate random names and continuously republish variants, which can lead to a significant increase in malicious packages within the npm registry. The ramifications include potential security risks for developers who unknowingly use these packages, as they may inadvertently integrate malicious code into their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall indah-keripik38-ruroIf 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 'indah-keripik38-ruro' package and monitor your project for any dependencies that may have inadvertently included it. Additionally, consider using tools like Vulert to monitor your package-lock.json file for vulnerabilities.
Conclusion
The 'indah-keripik38-ruro' package poses a significant threat due to its malicious code designed to manipulate npm registry entries. Developers are advised to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for indah-keripik38-ruro →
FAQ
The impact includes the potential for malicious code to be integrated into applications, leading to security breaches and compromised developer reputations.
You can use Vulert's playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.
If you have already used the 'indah-keripik38-ruro' package, it is crucial to remove it and check your application for any potential security issues.
Yes, tools like Vulert can help monitor your package-lock.json file for open-source vulnerabilities in real-time.
Regularly updating your dependencies, using trusted sources, and employing vulnerability monitoring tools can help prevent such issues.
