Malicious Code Injection in ocha-jus59-breki: A Threat to npm Ecosystem
Summary
MAL-2025-74687: Malicious code in ocha-jus59-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
ocha-jus59-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 aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm ecosystem.
Vulnerability Detail
The vulnerability in ocha-jus59-breki originates from its design to execute autopublish scripts that alter the package.json file. This includes removing private flags, changing version numbers, and generating random package names, which can lead to the proliferation of malicious packages in the npm registry. The ramifications of this vulnerability include potential security risks for developers who unknowingly install these packages, as well as damage to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ocha-jus59-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 measure, avoid using the ocha-jus59-breki package and monitor your project for any unintended installations. You can also use tools like Vulert to scan your package-lock.json file for vulnerabilities. To check if your application is affected, visit the Vulert playground at https://vulert.com/scanner.
Conclusion
The ocha-jus59-breki package poses a significant threat to the npm ecosystem due to its malicious code that alters package files and republish variants. It is essential for developers to be vigilant and remove any affected packages from their projects. Utilizing tools like Vulert can aid in monitoring and identifying vulnerabilities effectively.
See every vulnerability recorded for ocha-jus59-breki →
FAQ
ocha-jus59-breki is an npm package identified as part of a malicious campaign that modifies package files and republish variants to inflate developer reputation scores.
The vulnerability can lead to the installation of malicious packages, compromising the security and integrity of your project.
Immediately uninstall the package using 'npm uninstall ocha-jus59-breki' and review your project dependencies for any other malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
