Malicious Code Injection in miracle-doki-uikayananbubaki: A Threat to npm Ecosystem
Summary
MAL-2025-160527: Malicious code in miracle-doki-uikayananbubaki (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-uikayananbubaki' 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, such as package.json, leading to potential security risks.
Vulnerability Detail
The vulnerability in 'miracle-doki-uikayananbubaki' originates from its design to include autopublish scripts that alter package.json by removing private flags and changing version numbers. This behavior allows the package to generate random names, often themed around Indonesian culture, and continuously republish variants. The ramifications include pollution of the npm registry, making it difficult for developers to find legitimate packages, and potential exploitation of the modified packages by malicious actors.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall miracle-doki-uikayananbubakiIf 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 remove the package from your project by executing 'npm uninstall miracle-doki-uikayananbubaki'. This will prevent any malicious code from executing while you assess the situation.
Conclusion
The 'miracle-doki-uikayananbubaki' package poses a significant threat due to its malicious code that alters package.json and repopulates the npm registry with potentially harmful variants. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications.
See every vulnerability recorded for miracle-doki-uikayananbubaki →
FAQ
The vulnerability involves malicious code that modifies package.json to remove private flags and change version numbers, allowing for the creation of numerous derivative packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json, you can identify if your application is affected by this vulnerability.
If an immediate update is not possible, consider uninstalling the package as a temporary measure to mitigate risks.
Yes, Vulert provides a playground where you can check if your application is affected by this vulnerability without requiring any signup.
Long-term implications include potential exploitation of the modified packages, leading to security breaches and a polluted npm registry, which can hinder developers' ability to find legitimate packages.
