Malicious Code Injection in miracle-dibok-ikalaiku1 Package
Summary
MAL-2025-160467: Malicious code in miracle-dibok-ikalaiku1 (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The miracle-dibok-ikalaiku1 package is part of the npm ecosystem, typically used for various JavaScript applications. However, it 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. This package modifies its own metadata to facilitate the malicious behavior.
Vulnerability Detail
The vulnerability stems from the package's design, which includes autopublish scripts that remove private flags from package.json, alter version numbers, and generate random package names. This behavior leads to the pollution of the npm registry with numerous derivative packages, potentially compromising the integrity of the ecosystem and affecting developers relying on the npm registry for legitimate packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall miracle-dibok-ikalaiku1If 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 measure, you can avoid using the miracle-dibok-ikalaiku1 package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before installation.
Conclusion
The miracle-dibok-ikalaiku1 package poses a significant risk due to its malicious behavior of modifying package metadata and flooding the npm registry. It is essential to remove this package from your projects and utilize tools like Vulert to maintain the security of your software dependencies.
See every vulnerability recorded for miracle-dibok-ikalaiku1 →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry, making it difficult to find legitimate packages and potentially compromising your project's security.
You should uninstall the miracle-dibok-ikalaiku1 package immediately and check for any other affected packages in your project.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by visiting the Vulert playground.
Regularly audit your dependencies, use trusted packages, and consider using tools like Vulert to monitor for vulnerabilities in real-time.
