Malicious Code Injection in ocha-tomat15-breki: A Threat to npm Packages
Summary
MAL-2025-74723: Malicious code in ocha-tomat15-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 'ocha-tomat15-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and sharing of code among developers. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that can inflate developer reputation scores for token rewards. This vulnerability poses a significant risk to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability originates from a malicious payload embedded within the 'ocha-tomat15-breki' package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are often themed around Indonesian culture. The malicious scripts (auto.js, autopublish.js, etc.) continuously republish these variants, polluting the npm registry and potentially leading to the distribution of compromised packages to unsuspecting developers.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ocha-tomat15-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 remove the 'ocha-tomat15-breki' package from your project by executing the command: 'npm uninstall ocha-tomat15-breki'. This will prevent any malicious code from executing until a patch is available.
Conclusion
The 'ocha-tomat15-breki' package has been identified as a vector for malicious code injection, posing significant risks to developers using npm. It is essential to stay informed about vulnerabilities and take proactive measures to secure your applications. Regularly updating packages and utilizing tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for ocha-tomat15-breki →
FAQ
The main risk is that it can modify your package.json file and republish malicious variants, which can lead to the distribution of compromised software.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
If you have installed the 'ocha-tomat15-breki' package, it is recommended to uninstall it immediately and check for any updates or patches.
Currently, there is no specific patched version available for the 'ocha-tomat15-breki' package. Regularly check for updates from the package maintainers.
Using compromised packages can lead to security breaches, data loss, and damage to your application's reputation. It is crucial to ensure the integrity of all dependencies.
