Malicious Code Injection in kiki-rawon76-breki: A Threat to npm Ecosystem
Summary
MAL-2025-73887: Malicious code in kiki-rawon76-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
kiki-rawon76-breki is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which has been known to flood the npm ecosystem with derivative packages. The primary function of these packages is to inflate developer reputation scores through the automatic generation and publication of numerous variants with randomized names. This behavior poses significant risks to developers and users relying on npm packages.
Vulnerability Detail
The vulnerability in kiki-rawon76-breki stems from its malicious payload that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish itself and its variants, polluting the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms to manipulate package visibility and reputation. The ramifications include potential security risks for applications using these packages, as they may inadvertently incorporate malicious code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kiki-rawon76-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-rawon76-breki package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes or additions.
Conclusion
The kiki-rawon76-breki package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and republishing itself. It is essential for developers to be vigilant about the packages they use and to take immediate action to remove any affected packages. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for kiki-rawon76-breki →
FAQ
kiki-rawon76-breki is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.
You should uninstall the package immediately using npm uninstall kiki-rawon76-breki and check your project for any unauthorized changes.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
