Malicious Code Injection in ocha-rujak28-breki: A Threat to npm Ecosystem
Summary
MAL-2025-74707: Malicious code in ocha-rujak28-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-rujak28-breki' 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. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability in 'ocha-rujak28-breki' stems from its malicious code that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is part of a broader scheme to publish derivative packages that pollute the npm registry, potentially leading to security risks for applications that depend on these packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ocha-rujak28-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-rujak28-breki' package and replace it with a trusted alternative. Regularly audit your package dependencies using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The 'ocha-rujak28-breki' package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry with derivative packages. 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-rujak28-breki →
FAQ
The impact includes potential exposure to malicious code that can alter your project's package metadata and compromise security.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
Immediately uninstall the package using 'npm uninstall ocha-rujak28-breki' and audit your project for other vulnerabilities.
Yes, consider using well-established and trusted packages that serve similar functionalities without the associated risks.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to your packages.
