Malicious Code Injection in mutssrio-muiko-mutryi: A Threat to npm Ecosystem
Summary
MAL-2025-161179: Malicious code in mutssrio-muiko-mutryi (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 'mutssrio-muiko-mutryi' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish itself under various names, contributing to the pollution of the npm registry.
Vulnerability Detail
The vulnerability stems from the package's malicious payload, which alters the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these tainted packages, leading to potential security breaches and loss of trust in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mutssrio-muiko-mutryiIf 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, avoid using the 'mutssrio-muiko-mutryi' package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package-lock.json file to identify and remove any malicious packages.
Conclusion
The 'mutssrio-muiko-mutryi' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to ensure the security of their applications. By taking proactive measures, developers can protect their projects from potential vulnerabilities.
See every vulnerability recorded for mutssrio-muiko-mutryi →
FAQ
The package contains malicious code that modifies package.json files and republishes itself under various names, compromising the integrity of the npm registry.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
You should uninstall the package immediately using 'npm uninstall mutssrio-muiko-mutryi' and review your dependencies for any other malicious packages.
Yes, consider using other npm packages that provide similar functionality but do not have a history of malicious behavior. Always review the package's reputation and user feedback.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about the latest security advisories in the npm ecosystem.
