Malicious Code Injection in miracle-dok-uikaaki: A Threat to npm Ecosystem

miracle-dok-uikaaki Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160510: Malicious code in miracle-dok-uikaaki (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package miracle-dok-uikaaki is part of a broader campaign that exploits the npm ecosystem. It is associated with the tea.xyz token reward initiative, which has led to the proliferation of numerous malicious packages. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names, thereby compromising the integrity of the npm registry.

Vulnerability Detail

The vulnerability in miracle-dok-uikaaki stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. This behavior not only affects the reputation of developers but also poses a risk to users who may inadvertently install these compromised packages, leading to potential security breaches in their applications.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall miracle-dok-uikaaki

If 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-uikaaki package altogether until a secure version is released. Additionally, you can monitor your package-lock.json file for any unauthorized changes and remove any suspicious packages manually.

Conclusion

The miracle-dok-uikaaki package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to remain vigilant, update their packages regularly, and utilize monitoring tools like Vulert to safeguard their applications from potential vulnerabilities.

See every vulnerability recorded for miracle-dok-uikaaki →

Share this vulnerability

FAQ

miracle-dok-uikaaki is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your application.

If you have installed miracle-dok-uikaaki, it is recommended to remove it immediately and update your dependencies to ensure you are not using any compromised packages.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

To prevent future vulnerabilities, regularly update your dependencies, use trusted sources for packages, and consider employing automated tools to monitor for vulnerabilities.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall miracle-dok-uikaaki

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback