Malicious Code Injection in miracle-dokloi-ikak Package

miracle-dokloi-ikak Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160542: Malicious code in miracle-dokloi-ikak (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-dokloi-ikak package is part of the npm ecosystem, often utilized for various JavaScript applications. It is designed to facilitate the development and deployment of applications by providing reusable code components. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability in the miracle-dokloi-ikak package stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use 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-dokloi-ikak

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-dokloi-ikak package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall miracle-dokloi-ikak.

Conclusion

The miracle-dokloi-ikak package poses a significant security risk due to its malicious behavior of modifying package files and flooding the npm registry. It is crucial for developers to remove this package and monitor their applications for vulnerabilities to maintain security and integrity.

See every vulnerability recorded for miracle-dokloi-ikak →

Share this vulnerability

FAQ

The miracle-dokloi-ikak package is an npm package used in JavaScript applications, but it has been identified as part of a malicious campaign.

Using the miracle-dokloi-ikak package can lead to security breaches as it modifies package.json and floods the npm registry with malicious packages.

You should uninstall the miracle-dokloi-ikak package immediately and look for alternative packages to avoid potential security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.

Regularly update your dependencies, use tools like Vulert for monitoring, and review package sources before installation to mitigate risks.

How To Fix

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

npm uninstall miracle-dokloi-ikak

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