Malicious Code Injection in joko-moci5-breki: A Threat to npm Packages
Summary
MAL-2025-73750: Malicious code in joko-moci5-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 package 'joko-moci5-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 identified as malicious. It is designed to manipulate the npm registry by generating and publishing numerous derivative packages with altered metadata, thus inflating developer reputation scores for token rewards. The presence of such malicious packages poses a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in 'joko-moci5-breki' originates from its association with the tea.xyz token reward campaign. The malicious code embedded in this package modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of these variants, which pollutes the npm registry and can compromise the integrity of other packages. Developers using this package may unknowingly expose their applications to security risks and reputation damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joko-moci5-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, consider using a package-lock.json file to lock your dependencies to known safe versions. This can help prevent the installation of malicious packages. You can also monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for any open-source vulnerabilities.
Conclusion
The 'joko-moci5-breki' package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.
See every vulnerability recorded for joko-moci5-breki →
FAQ
The main issue is that it contains malicious code that modifies package metadata and floods the npm registry with derivative packages.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
You should uninstall the package immediately using 'npm uninstall joko-moci5-breki' and review your project's dependencies for any other vulnerabilities.
Currently, there is no specific patched version available for the joko-moci5-breki package, so it is recommended to remove it entirely.
Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities, helping you maintain a secure application.
