Malicious Code Injection in miracle-diook-ikukunma1: A Threat to npm Users
Summary
MAL-2025-160495: Malicious code in miracle-diook-ikukunma1 (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-diook-ikukunma1' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files, such as package.json, leading to potential security risks for users.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which alters the package.json file to remove private flags, changes version numbers, and generates random package names. This behavior not only pollutes the npm registry but also compromises the integrity of the user's project by allowing unauthorized access and modifications. The continuous republishing of these variants can lead to a significant increase in the attack surface for developers relying on npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall miracle-diook-ikukunma1If 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 prevent the installation of this malicious package by using npm's package-lock.json file to lock your dependencies. Ensure that your package-lock.json does not include 'miracle-diook-ikukunma1'. You can also use Vulert to monitor your project for vulnerabilities without needing to install any additional software. Simply upload your package-lock.json to Vulert's playground at https://vulert.com/scanner to check for vulnerabilities.
Conclusion
The 'miracle-diook-ikukunma1' package poses a significant threat to npm users due to its malicious code that alters critical project files. By understanding the nature of this vulnerability and taking proactive steps to remove the package and monitor your dependencies, you can safeguard your projects from potential attacks.
See every vulnerability recorded for miracle-diook-ikukunma1 →
FAQ
The primary risk is the modification of package.json, which can lead to unauthorized access and the proliferation of malicious variants in the npm registry.
You can use Vulert's playground to analyze your package-lock.json file for vulnerabilities, including the presence of miracle-diook-ikukunma1.
Uninstall the package immediately using 'npm uninstall miracle-diook-ikukunma1' and review your other dependencies for potential vulnerabilities.
Yes, Vulert provides real-time monitoring of open-source vulnerabilities using just your package-lock.json file.
It is recommended to check for vulnerabilities regularly, especially after adding new packages or updating existing ones.
