Malicious Code Injection in irma-kripik71-ruro: A Threat to npm Packages
Summary
MAL-2025-104394: Malicious code in irma-kripik71-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-kripik71-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. These packages often contain scripts that automatically publish derivative versions with altered metadata, aimed at inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in 'irma-kripik71-ruro' stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. This behavior can compromise the integrity of the npm ecosystem, allowing for potential exploitation by malicious actors who can leverage these packages for nefarious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall irma-kripik71-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 affected package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The 'irma-kripik71-ruro' package poses a significant risk due to its malicious behavior, which can compromise the npm ecosystem. It is crucial for developers to take immediate action by removing the package and monitoring their dependencies for vulnerabilities. Utilizing tools like Vulert can further enhance security measures.
See every vulnerability recorded for irma-kripik71-ruro →
FAQ
The vulnerability can lead to the pollution of the npm registry, compromising the integrity of package management and potentially allowing malicious actors to exploit these packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can determine if your application is affected by this vulnerability.
If you have installed 'irma-kripik71-ruro', you should uninstall it immediately using 'npm uninstall irma-kripik71-ruro' and check for alternative packages.
Yes, tools like Vulert can help you monitor your npm packages for vulnerabilities without requiring code access or installation.
Regularly update your packages, use tools like Vulert to monitor vulnerabilities, and review package metadata and reputation before installation.
