Malicious Code Injection in ocha-naget85-breki: A Threat to npm Users
Summary
MAL-2025-74703: Malicious code in ocha-naget85-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-naget85-breki' is part of a broader campaign that exploits the npm ecosystem, specifically targeting developers involved in the tea.xyz token reward initiative. This package is designed to automate the generation and publication of derivative packages, which can mislead users and inflate developer reputation scores. Its functionality is compromised by malicious scripts that alter package metadata, making it a significant threat to the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'ocha-naget85-breki' originates from its association with the tea.xyz token reward campaign, which floods npm with malicious packages. The malicious payload modifies the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, polluting the npm registry. This behavior can lead to confusion among developers, potential security risks, and a degradation of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ocha-naget85-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-naget85-breki' package altogether. If you have already installed it, ensure to monitor your package-lock.json for any unauthorized changes and consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The 'ocha-naget85-breki' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry with unauthorized packages. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can enhance your ability to manage and mitigate such risks effectively.
See every vulnerability recorded for ocha-naget85-breki →
FAQ
The primary risk is the modification of package.json, which can lead to unauthorized access and the proliferation of malicious packages in the npm registry.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By uploading your package-lock.json file to the Vulert playground, you can check for vulnerabilities without any signup.
Immediately uninstall the package using 'npm uninstall ocha-naget85-breki' and monitor your project for any unauthorized changes.
Currently, there are no specific patches for the ocha-naget85-breki package. The best course of action is to remove it and monitor for updates.
Vulert uses your package-lock.json to provide real-time monitoring and alerts for vulnerabilities, helping you maintain the security of your software without needing to access the code or install additional tools.
