Malicious Code Injection in miracle-dibok-ikalabaliku1: A Threat to npm Ecosystem

miracle-dibok-ikalabaliku1 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160465: Malicious code in miracle-dibok-ikalabaliku1 (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-dibok-ikalabaliku1' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards in the tea protocol, making it a significant concern for developers relying on npm for package management.

Vulnerability Detail

The vulnerability in 'miracle-dibok-ikalabaliku1' involves malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of other packages. The origin of this vulnerability is linked to automated scripts that facilitate the creation of these malicious packages, which can lead to reputational damage for developers and security risks for applications utilizing these packages.

How To Fix

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

npm uninstall miracle-dibok-ikalabaliku1

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 workaround, you can manually check your package-lock.json file for any instances of 'miracle-dibok-ikalabaliku1' and remove it. You can use the following command to uninstall the package: npm uninstall miracle-dibok-ikalabaliku1.

Conclusion

The 'miracle-dibok-ikalabaliku1' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is essential for developers to be vigilant and remove such packages to maintain the integrity and security of their applications. Utilizing tools like Vulert can help in monitoring for vulnerabilities effectively.

See every vulnerability recorded for miracle-dibok-ikalabaliku1 →

Share this vulnerability

FAQ

'miracle-dibok-ikalabaliku1' is an npm package involved in a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your application and exposing it to security risks.

You should uninstall 'miracle-dibok-ikalabaliku1' immediately to prevent any potential security risks.

Currently, there is no patched version available. The best course of action is to remove the package from your project.

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

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-dibok-ikalabaliku1

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