Malicious Code Injection in dono-kripik31-ruro Package - npm Vulnerability
Summary
MAL-2025-101715: Malicious code in dono-kripik31-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The dono-kripik31-ruro package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of such packages is to manipulate developer reputation scores through automated publishing scripts, leading to a polluted npm registry.
Vulnerability Detail
The vulnerability in the dono-kripik31-ruro package stems from its malicious code that modifies the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dono-kripik31-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 workaround, you can avoid using the dono-kripik31-ruro package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file to alert you of any open-source vulnerabilities in real-time.
Conclusion
The dono-kripik31-ruro package presents a significant security risk due to its malicious code that alters project files and repopulates the npm registry with compromised packages. It is crucial for developers to remove this package and utilize tools like Vulert to monitor their projects for vulnerabilities.
See every vulnerability recorded for dono-kripik31-ruro →
FAQ
The dono-kripik31-ruro package is an npm package associated with a token reward campaign that has been identified as malicious.
The malicious code modifies your package.json file, potentially compromising your project's integrity and security.
You should remove the dono-kripik31-ruro package from your project and monitor for any updates or patches.
Yes, you can use Vulert's playground to analyze your package-lock.json file for vulnerabilities without needing to sign up.
Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file, ensuring you stay informed about potential risks.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
