Malicious Code Injection in miracle-dokloi-ikaluk Package

miracle-dokloi-ikaluk Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160544: Malicious code in miracle-dokloi-ikaluk (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-ikaluk package is part of the npm ecosystem, often utilized in various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package, like others in the campaign, is designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names.

Vulnerability Detail

The vulnerability in the miracle-dokloi-ikaluk package stems from its malicious payload, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only compromises the integrity of the npm ecosystem but can also lead to unintentional use of these malicious packages by developers, potentially exposing their applications to further vulnerabilities.

How To Fix

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

npm uninstall miracle-dokloi-ikaluk

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, avoid using the miracle-dokloi-ikaluk package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file to alert you of any open-source vulnerabilities in real-time.

Conclusion

The miracle-dokloi-ikaluk package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain application security.

See every vulnerability recorded for miracle-dokloi-ikaluk →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.

The vulnerability can lead to the unintentional use of malicious code, compromising your application's security and integrity.

You should uninstall the miracle-dokloi-ikaluk package immediately and check for any dependencies that may be affected.

Yes, you can use Vulert to monitor your package-lock.json file for open-source vulnerabilities in real-time without needing to install any software.

Absolutely! You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without signing up.

How To Fix

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

npm uninstall miracle-dokloi-ikaluk

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