Malicious Code Injection in kiki-donat34-breki: A Threat to npm Users
Summary
MAL-2025-73848: Malicious code in kiki-donat34-breki (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 kiki-donat34-breki is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, making them a significant threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in kiki-donat34-breki originates from its association with the tea.xyz token reward campaign. The package contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of applications that depend on these packages. The malicious payload can affect developers' reputations and the overall trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kiki-donat34-brekiIf 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 kiki-donat34-breki package and any other packages that may be associated with the tea.xyz campaign. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by visiting the Vulert playground at https://vulert.com/scanner without needing to sign up.
Conclusion
The kiki-donat34-breki package poses a significant threat to the npm ecosystem due to its malicious code that alters package metadata and floods the registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity and security of their applications.
See every vulnerability recorded for kiki-donat34-breki →
FAQ
kiki-donat34-breki is an npm package identified as part of a malicious campaign that floods the npm registry with derivative packages.
The vulnerability can lead to the pollution of the npm registry and compromise the security of applications that depend on affected packages.
You should uninstall the kiki-donat34-breki package immediately and check for any updates to your other dependencies.
You can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. Visit https://vulert.com for more information.
Regularly updating your dependencies and using tools like Vulert can help you stay informed about potential vulnerabilities in your project.
