Malicious Code Injection in miracle-dibook-ikaku1 Package
Summary
MAL-2025-160479: Malicious code in miracle-dibook-ikaku1 (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-dibook-ikaku1 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the distribution of content or applications but has been compromised. It is known for its functionality in generating and publishing derivative packages, which are intended to enhance developer reputation scores for token rewards. However, its vulnerability has led to malicious behavior that affects the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the miracle-dibook-ikaku1 package stems from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall miracle-dibook-ikaku1If 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-ikaku1 package until a patched version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The miracle-dibook-ikaku1 package has been identified as having a significant vulnerability due to its association with malicious code that affects the npm registry. It is essential for developers to take proactive measures by updating or removing the package and utilizing tools like Vulert for ongoing monitoring of vulnerabilities in their applications.
See every vulnerability recorded for miracle-dibook-ikaku1 →
FAQ
The miracle-dibook-ikaku1 package is an npm package that was part of a token reward campaign, designed to generate and publish derivative packages.
The vulnerability can lead to the introduction of malicious code in your application, potentially compromising its security and integrity.
If you have used the miracle-dibook-ikaku1 package, it is crucial to update it to the latest version or remove it from your project to prevent security risks.
Yes, you can use Vulert to monitor your application for open-source vulnerabilities in real-time by analyzing your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
