Malicious Code Injection in utomo-kue2-miaww: A Threat to npm Ecosystem
Summary
MAL-2025-91581: Malicious code in utomo-kue2-miaww (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 'utomo-kue2-miaww' 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 linked to a series of malicious activities aimed at inflating developer reputation scores. The functionality of this package is compromised, leading to potential risks for developers and users relying on it.
Vulnerability Detail
The vulnerability in 'utomo-kue2-miaww' stems 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 can lead to a loss of trust in the npm ecosystem and expose users to further malicious activities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall utomo-kue2-miawwIf 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 'utomo-kue2-miaww' package and 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 can analyze your package-lock.json file for any open-source vulnerabilities.
Conclusion
The 'utomo-kue2-miaww' package poses a significant threat due to its malicious code that manipulates package metadata and floods the npm registry. It is essential for developers to remove this package and monitor their projects for vulnerabilities to maintain a secure development environment.
See every vulnerability recorded for utomo-kue2-miaww →
FAQ
The main issue is that it contains malicious code designed to manipulate package metadata and flood the npm registry with derivative packages.
You can use Vulert to monitor your project for vulnerabilities by analyzing the package-lock.json file. Visit Vulert Scanner to check for any affected packages.
Using compromised packages can lead to security breaches, data leaks, and a loss of trust in the software supply chain.
To prevent future vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated with security advisories.
If you have used this package in production, it is crucial to remove it immediately and replace it with a secure alternative. Monitor your application for any unusual behavior.
