Malicious Code Injection in ade-kripik42-ruro: A Threat to npm Ecosystem
Summary
MAL-2025-99144: Malicious code in ade-kripik42-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 'ade-kripik42-ruro' is part of a larger set of npm packages that have been identified as malicious. These packages are associated with the tea.xyz token reward campaign, which aims to inflate developer reputation scores by flooding the npm registry with derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish itself under various names, thereby compromising the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'ade-kripik42-ruro' originates from its design to include autopublish scripts that automatically generate and publish derivative packages with randomized names. This behavior not only pollutes the npm registry but also modifies the package.json file by removing private flags and altering version numbers. The continuous republishing of these variants can lead to significant security risks, including the potential for malicious actors to exploit these packages for nefarious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ade-kripik42-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 prevent the installation of this package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. However, the best course of action is to remove the package entirely.
Conclusion
The 'ade-kripik42-ruro' package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package files and republishing itself. It is crucial for developers to take immediate action to remove this package and monitor their projects for similar vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for ade-kripik42-ruro →
FAQ
The primary risk is that it modifies your package.json file and repopulates the npm registry with potentially harmful packages, which can lead to security vulnerabilities in your application.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check your application without any signup.
You should immediately uninstall the package using 'npm uninstall ade-kripik42-ruro' and check for any dependencies that may be affected.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time. Keeping your packages updated can also help mitigate risks.
If you experience issues, review your project's dependencies and ensure that no other packages are relying on 'ade-kripik42-ruro'. You may need to find alternatives for any functionality it provided.
