Malicious Code Exploit in ocha-rojak60-breki Package
Summary
MAL-2025-74706: Malicious code in ocha-rojak60-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 ocha-rojak60-breki package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of this package is to facilitate the automatic generation and publishing of derivative packages, which can lead to reputation inflation for developers involved in the tea protocol token rewards.
Vulnerability Detail
The vulnerability in the ocha-rojak60-breki package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising the integrity of other packages. This behavior can lead to security risks for developers and users relying on npm packages, as it undermines the trustworthiness of the registry.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ocha-rojak60-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 ocha-rojak60-breki package and any packages that depend on it. Monitor your package-lock.json file for any unexpected changes and remove any suspicious packages immediately.
Conclusion
The ocha-rojak60-breki package poses a significant security risk due to its malicious code that alters package metadata and repopulates the npm registry with harmful variants. It is crucial for developers to remove this package and monitor their dependencies to maintain the security of their applications.
See every vulnerability recorded for ocha-rojak60-breki →
FAQ
The ocha-rojak60-breki package is an npm package associated with a token reward campaign that has been found to contain malicious code.
The malicious code modifies your package.json file, removes private flags, and republishes variants that can compromise the integrity of your project and the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
You should uninstall the package immediately using 'npm uninstall ocha-rojak60-breki' and review your other dependencies for security.
Regularly update your dependencies, monitor your package-lock.json file for changes, and use tools like Vulert to stay informed about vulnerabilities.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
