Malicious Code Injection in eka-soto78-ruro: A Threat to npm Packages

eka-soto78-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101932: Malicious code in eka-soto78-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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'eka-soto78-ruro' is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for rewards associated with the tea protocol, making it a significant concern for developers relying on npm for package management.

Vulnerability Detail

The vulnerability in 'eka-soto78-ruro' stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This not only pollutes the npm registry but also poses a risk of unintentional dependency on malicious packages by developers. The origin of this vulnerability is linked to the broader trend of malicious packages flooding the npm ecosystem, specifically targeting the tea.xyz token reward campaign.

How To Fix

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

npm uninstall eka-soto78-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 avoid using the 'eka-soto78-ruro' package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your npm packages using tools like 'npm audit' to identify and remove any potentially harmful packages.

Conclusion

The 'eka-soto78-ruro' package poses a significant risk due to its malicious code designed to manipulate the npm registry. Developers should take immediate action to remove this package and monitor their dependencies for similar vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your projects.

See every vulnerability recorded for eka-soto78-ruro →

Share this vulnerability

FAQ

The 'eka-soto78-ruro' package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.

This vulnerability can lead to the pollution of your project's dependencies with malicious packages, potentially compromising the security and integrity of your application.

If you have installed the 'eka-soto78-ruro' package, you should uninstall it immediately using 'npm uninstall eka-soto78-ruro' and audit your project for other malicious dependencies.

You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.

Yes, tools like 'npm audit' can help you identify vulnerabilities in your npm packages. Additionally, Vulert provides a user-friendly interface for monitoring vulnerabilities without requiring code access.

How To Fix

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

npm uninstall eka-soto78-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