Malicious Code Injection in irma-bika25-ruro: A Threat to npm Packages
Summary
MAL-2025-104383: Malicious code in irma-bika25-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 'irma-bika25-ruro' 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 the npm ecosystem for token rewards, leading to potential security risks for developers and users.
Vulnerability Detail
The vulnerability in 'irma-bika25-ruro' arises from its inclusion in a malicious campaign that employs scripts to automatically generate and publish derivative packages with randomized names. These scripts modify the package.json file to remove private flags, alter version numbers, and continuously republish variants, thereby polluting the npm registry. This behavior can lead to compromised developer reputations and the potential for malicious code to be executed in applications that depend on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall irma-bika25-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 measure, you can avoid using the 'irma-bika25-ruro' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using npm audit to identify and address vulnerabilities in your project.
Conclusion
The 'irma-bika25-ruro' package poses a significant security risk due to its malicious code designed to manipulate the npm ecosystem. Developers should take immediate action to remove this package and monitor their applications for vulnerabilities using tools like Vulert.
See every vulnerability recorded for irma-bika25-ruro →
FAQ
The vulnerability involves malicious code that modifies package.json and repackages the software to inflate developer reputation scores.
You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
It is advisable to remove the package immediately and look for alternatives. You can also run npm audit to identify other vulnerabilities.
Yes, it can lead to compromised developer reputations and the potential execution of malicious code in dependent applications.
Currently, there is no specific patch for 'irma-bika25-ruro'. The best course of action is to remove the package until a safe version is released.
