Malicious Code Injection in ocha-tumis67-ruro: A Threat to npm Ecosystem
Summary
MAL-2025-106548: Malicious code in ocha-tumis67-ruro (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-tumis67-ruro' 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 the npm registry and inflate developer reputation scores through automated publishing of derivative packages.
Vulnerability Detail
The vulnerability in 'ocha-tumis67-ruro' stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to continuously republish variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits the npm registry for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall ocha-tumis67-ruroIf 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-tumis67-ruro' package and any other packages associated with the tea.xyz campaign. Monitor your package dependencies and remove any that are suspicious or unverified.
Conclusion
The 'ocha-tumis67-ruro' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package publishing. It is crucial for developers to remove this package and monitor their dependencies to maintain the integrity of their projects.
See every vulnerability recorded for ocha-tumis67-ruro →
FAQ
The impact includes potential pollution of the npm registry, which can lead to compromised developer reputation and integrity of the packages.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
There is no patch for 'ocha-tumis67-ruro' as it is recommended to remove the package entirely from your project.
If you have used 'ocha-tumis67-ruro', uninstall it immediately and review your project for any other potentially malicious packages.
Regularly audit your dependencies, use trusted sources for packages, and employ tools like Vulert for ongoing monitoring of vulnerabilities.
