Malicious Code Injection in miracle-dokoi-uniaaw: A Threat to npm Users

miracle-dokoi-uniaaw Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160560: Malicious code in miracle-dokoi-uniaaw (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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The 'miracle-dokoi-uniaaw' package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages flooding the npm registry. These packages are designed to inflate developer reputation scores through automatic publishing of derivative packages with randomized names.

Vulnerability Detail

The vulnerability in 'miracle-dokoi-uniaaw' stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names and continuously republishes variants, leading to pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may introduce security risks and instability in their applications.

How To Fix

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

npm uninstall miracle-dokoi-uniaaw

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-dokoi-uniaaw' package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The 'miracle-dokoi-uniaaw' package poses significant risks due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is essential for developers to remove this package and regularly audit their dependencies to maintain the security and integrity of their applications.

See every vulnerability recorded for miracle-dokoi-uniaaw →

Share this vulnerability

FAQ

The package contains malicious code that modifies package.json files and republishes variants to pollute the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application using the Vulert playground at Vulert Scanner.

Immediately remove the 'miracle-dokoi-uniaaw' package from your project and check for any other affected packages.

Yes, tools like npm audit and Vulert can help identify and manage vulnerabilities in your npm packages.

Using compromised packages can lead to security breaches, data loss, and instability in your applications.

How To Fix

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

npm uninstall miracle-dokoi-uniaaw

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