Malicious Code Injection in irma-sate77-ruro: A Threat to npm Packages
Summary
MAL-2025-104411: Malicious code in irma-sate77-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-sate77-ruro' is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to automatically generate and publish derivative packages with randomized names, which can lead to reputation inflation for developers involved in the tea.xyz token reward scheme.
Vulnerability Detail
The vulnerability in 'irma-sate77-ruro' originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, change version numbers, and generate random names, thereby polluting the npm registry. The ramifications include potential security risks for users who unknowingly install these malicious packages, as they may inadvertently execute harmful code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall irma-sate77-ruro
If 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 'irma-sate77-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-sate77-ruro' package poses significant security risks due to its malicious nature. Users are advised to remove this package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can enhance your security posture by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for irma-sate77-ruro →
FAQ
The primary risk is the potential execution of malicious code that can compromise your application and its data.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
You should immediately remove the package from your project and check for any malicious activity that may have occurred.
Yes, tools like Vulert can help monitor your dependencies for vulnerabilities and provide alerts in real-time.
Regularly audit your dependencies using tools like npm audit, and stay informed about the packages you use by following security advisories.