Malicious Code Injection in eko-botok8-ruro Package - npm Vulnerability

eko-botok8-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101941: Malicious code in eko-botok8-ruro (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The eko-botok8-ruro package is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages. This behavior is intended to inflate developer reputation scores for token rewards, but it also poses significant risks to users and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the eko-botok8-ruro package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising the security of applications that depend on this package. The origin of this vulnerability is linked to a broader trend of malicious packages flooding the npm ecosystem, specifically targeting users involved in the tea protocol token rewards.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall eko-botok8-ruro

If 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 eko-botok8-ruro package from your dependencies by executing the following command: npm uninstall eko-botok8-ruro. This will help prevent any potential exploitation while you assess alternative packages or wait for a fix.

Conclusion

The eko-botok8-ruro package contains a serious vulnerability that can compromise the security of applications relying on it. It is crucial to take immediate action by updating or removing the package to safeguard your project. Utilizing tools like Vulert can further enhance your security posture by providing real-time vulnerability alerts.

See every vulnerability recorded for eko-botok8-ruro →

Share this vulnerability

FAQ

The eko-botok8-ruro package is an npm package associated with the tea.xyz token reward campaign, designed to manipulate the npm registry.

This vulnerability can compromise the integrity of your application by introducing malicious code that alters package configurations and floods the npm registry.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities at the Vulert playground.

If you cannot update the package, consider removing it from your project and looking for alternative packages that provide similar functionality without the associated risks.

Regularly audit your dependencies, keep them updated, and utilize tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall eko-botok8-ruro

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback