Malicious Code Injection in miracle-doki-uiknki: A Threat to npm Packages
Summary
MAL-2025-160530: Malicious code in miracle-doki-uiknki (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-uiknki' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores. Its functionality is compromised due to the presence of malicious code that alters package metadata.
Vulnerability Detail
The vulnerability in 'miracle-doki-uiknki' originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of integrity in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall miracle-doki-uiknkiIf 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, you can avoid using the 'miracle-doki-uiknki' package until a fix is released. Additionally, you can monitor your package dependencies using tools like Vulert, which allows you to check for vulnerabilities in your application without requiring code access. You can use the Vulert playground at https://vulert.com/scanner to see if your application is affected by this vulnerability.
Conclusion
The 'miracle-doki-uiknki' package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for miracle-doki-uiknki →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative packages.
The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.
You should update the package to a patched version if available or remove it from your project until a fix is released.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.
