Malicious Code Injection in ocha-klipo59-breki: A Threat to npm Packages
Summary
MAL-2025-74691: Malicious code in ocha-klipo59-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'ocha-klipo59-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is linked to a token reward campaign that has been known to flood the npm registry with malicious packages. It is designed to automatically generate and publish derivative packages, which can lead to reputation inflation for developers involved in the tea protocol token rewards. The presence of such malicious packages poses a significant risk to the integrity of the npm registry and the security of applications relying on these packages.
Vulnerability Detail
The vulnerability in 'ocha-klipo59-breki' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to continuously republish variants, polluting the npm registry and potentially compromising the security of applications that depend on these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits the npm ecosystem for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ocha-klipo59-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
Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the affected package from your project. It is advisable to monitor your dependencies closely and avoid using packages that are part of known malicious campaigns.
Conclusion
The 'ocha-klipo59-breki' package poses a significant security risk due to its malicious code designed to manipulate package metadata and republish variants. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their dependencies.
See every vulnerability recorded for ocha-klipo59-breki →
FAQ
The main risk is that it contains malicious code that can modify your project's package.json file, leading to potential security vulnerabilities and pollution of the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By uploading your package-lock.json file, you can check for vulnerabilities without needing to access the code.
You should uninstall the package immediately using 'npm uninstall ocha-klipo59-breki' and review your other dependencies for any similar vulnerabilities.
Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and ensure you only use packages from trusted sources.
Vulert is a tool that helps monitor and alert for open-source vulnerabilities in your software. You can check your application for vulnerabilities using the Vulert playground without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
