Malicious Code Injection in miracle-dibok-i1: A Threat to npm Packages
Summary
MAL-2025-160463: Malicious code in miracle-dibok-i1 (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 package miracle-dibok-i1 is part of a series of npm packages that have been identified as part of a malicious campaign associated with the tea.xyz token reward initiative. These packages are designed to inflate developer reputation scores by automatically generating and publishing numerous derivative packages with randomized names. The malicious nature of this package lies in its ability to alter package metadata and continuously republish variants, thereby polluting the npm registry.
Vulnerability Detail
The vulnerability in miracle-dibok-i1 originates from its inclusion in a malicious campaign that utilizes autopublish scripts to modify package.json files. This modification removes private flags, alters version numbers, and generates random package names, which can lead to significant pollution of the npm registry. The ramifications include compromised package integrity, potential security risks for developers using these packages, and a general degradation of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall miracle-dibok-i1If 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-i1 package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your npm packages using tools like npm audit to identify and mitigate potential vulnerabilities.
Conclusion
The miracle-dibok-i1 package poses a significant threat due to its malicious code designed to manipulate package metadata and republish variants. It is essential for developers to remain vigilant, regularly audit their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can protect your projects from potential risks associated with this and similar vulnerabilities.
See every vulnerability recorded for miracle-dibok-i1 →
FAQ
miracle-dibok-i1 is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.
The vulnerability can lead to the modification of your package.json file, potentially compromising your project's integrity and security by introducing untrusted packages.
You should uninstall the package immediately using the command: npm uninstall miracle-dibok-i1 and review your project's dependencies for any other malicious packages.
You can use tools like npm audit to check for vulnerabilities in your project. Additionally, Vulert can help monitor and alert you in real-time for open-source vulnerabilities using just your package-lock.json.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
