Malicious Code Injection in kiki-miemee12-breki Package - npm Vulnerability
Summary
MAL-2025-73875: Malicious code in kiki-miemee12-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 kiki-miemee12-breki package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, making the package a potential threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability originates from the malicious code embedded within the kiki-miemee12-breki package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for developers using these packages, and a compromised reputation system within the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kiki-miemee12-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, avoid using the kiki-miemee12-breki package and monitor your dependencies for any malicious activity. You can also use tools like Vulert to check for vulnerabilities in your package-lock.json file.
Conclusion
The kiki-miemee12-breki package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package from their projects and monitor their dependencies for any vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.
See every vulnerability recorded for kiki-miemee12-breki →
FAQ
It is an npm package that is part of a malicious campaign to inflate developer reputation scores by flooding the npm registry with derivative packages.
The vulnerability can lead to the pollution of the npm registry and may introduce security risks if your project depends on these malicious packages.
You should uninstall the kiki-miemee12-breki package immediately using the command: npm uninstall kiki-miemee12-breki.
You can use Vulert to monitor your package-lock.json file for open-source vulnerabilities in real-time without needing to access the code.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
