Malicious Code Injection in miracle-dibook-ikukaai1 Package

miracle-dibook-ikukaai1 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160488: Malicious code in miracle-dibook-ikukaai1 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The miracle-dibook-ikukaai1 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards through various scripts that automate the publishing of derivative packages. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the miracle-dibook-ikukaai1 package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to pollution of the npm registry and potential reputational damage for developers. The origin of this issue is linked to a broader campaign that exploits npm for token rewards, making it a significant concern for developers relying on the integrity of package management systems.

How To Fix

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

npm uninstall miracle-dibook-ikukaai1

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-dibook-ikukaai1 package altogether. If it is already in use, consider removing it from your dependencies and replacing it with a trusted alternative. 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-dibook-ikukaai1 package has been identified as containing malicious code that poses a significant risk to developers and the npm ecosystem. It is crucial to remove this package from your projects and monitor for any updates or patches. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.

See every vulnerability recorded for miracle-dibook-ikukaai1 →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automate the publishing of derivative packages.

The malicious code modifies your package.json file, removes private flags, and republishes variants, potentially compromising your project's integrity and security.

You should remove the miracle-dibook-ikukaai1 package from your project and monitor for any updates or patches.

You can use Vulert, which allows you to check your package-lock.json file for vulnerabilities without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without signing up.

How To Fix

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

npm uninstall miracle-dibook-ikukaai1

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