Malicious Code Injection in miracle-doki-uini: A Threat to npm Users
Summary
MAL-2025-160531: Malicious code in miracle-doki-uini (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 'miracle-doki-uini' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, aimed at inflating developer reputation scores for token rewards. Its functionality is compromised due to malicious scripts that alter package metadata and republish variants, leading to potential abuse of the npm registry.
Vulnerability Detail
The vulnerability in 'miracle-doki-uini' originates from its involvement in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants, polluting the npm registry. This can lead to a loss of trust in the npm ecosystem, potential security risks for users who unknowingly install these packages, and a significant increase in spam within the registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall miracle-doki-uiniIf 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 'miracle-doki-uini' package until a secure version is released. Additionally, consider using npm audit to identify and address vulnerabilities in your project dependencies.
Conclusion
The 'miracle-doki-uini' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with spam. Users are advised to update their dependencies and utilize tools like Vulert to monitor for vulnerabilities effectively.
See every vulnerability recorded for miracle-doki-uini →
FAQ
The vulnerability can lead to the installation of malicious packages that compromise the integrity of your application and the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
If you have installed this package, it is crucial to remove it and update to a secure version as soon as possible.
While specific exploits may not be publicly documented, the nature of the vulnerability suggests that it can be exploited to publish malicious packages.
Vulert uses your package-lock.json to monitor for vulnerabilities in real-time, providing alerts for any open-source vulnerabilities detected in your software.
