Malicious Code Injection in miracle-dok-uikayaabaki: A Threat to npm Packages
Summary
MAL-2025-160512: Malicious code in miracle-dok-uikayaabaki (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'miracle-dok-uikayaabaki' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, making the package a potential vector for malicious activities.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of these variants, leading to pollution of the npm registry and potential exploitation by malicious actors. The presence of autopublish scripts (auto.js, autopublish.js, autopublish2.js, autopublish3.js) further exacerbates the risk, as they automate the process of creating and publishing these harmful packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall miracle-dok-uikayaabakiIf 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-dok-uikayaabaki' package and monitor your project for any dependencies that may have been affected by this vulnerability. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'miracle-dok-uikayaabaki' 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 remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your open-source dependencies.
See every vulnerability recorded for miracle-dok-uikayaabaki →
FAQ
The main issue is that it contains malicious code that modifies package.json and floods the npm registry with harmful packages.
You can check your package.json and package-lock.json files for the presence of 'miracle-dok-uikayaabaki'.
You should uninstall the package immediately using 'npm uninstall miracle-dok-uikayaabaki' and monitor for any other affected dependencies.
Regularly audit your dependencies using tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
