Malicious Code Injection in miracle-dok-ujai: A Threat to npm Users

miracle-dok-ujai Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160519: Malicious code in miracle-dok-ujai (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-ujai' is part of the npm ecosystem and appears to be associated with the tea.xyz token reward campaign. This package is designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. It is primarily used to inflate developer reputation scores for token rewards, making it a potential threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'miracle-dok-ujai' stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and creates random package names, which leads to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to 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-ujai

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-ujai' package and monitor your project for any dependencies that may have included it. You can also use tools like Vulert to check for vulnerabilities in your package-lock.json file. Here’s how to check your application: Visit the Vulert playground at https://vulert.com/scanner and upload your package-lock.json file to see if your application is affected by this vulnerability.

Conclusion

The 'miracle-dok-ujai' package poses a significant threat to npm users due to its malicious behavior of modifying package files and republishing variants. It is crucial to remove this package from your projects and utilize tools like Vulert to monitor for vulnerabilities in your dependencies.

See every vulnerability recorded for miracle-dok-ujai →

Share this vulnerability

FAQ

'miracle-dok-ujai' is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.

The vulnerability can lead to the introduction of malicious code in your application, potentially compromising its security and integrity.

You should uninstall the package immediately using 'npm uninstall miracle-dok-ujai' and check your project for any dependencies that may have included it.

You can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. Visit https://vulert.com for more information.

Yes, tools like Vulert can help you identify vulnerabilities by analyzing your package-lock.json file without requiring access to your code or installation.

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-ujai

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