Malicious Code Injection in eka-serimuka65-ruro: A Threat to npm Users

eka-serimuka65-ruro Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101931: Malicious code in eka-serimuka65-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'eka-serimuka65-ruro' is part of a broader campaign targeting npm users, linked to the tea.xyz token reward system. This package is designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names, which can mislead developers and inflate reputation scores. Its malicious nature poses significant risks to developers relying on npm for package management.

Vulnerability Detail

The vulnerability in 'eka-serimuka65-ruro' stems from its inclusion in a malicious campaign that utilizes autopublish scripts to alter package.json files. These scripts remove private flags, change version numbers, and generate random package names, leading to the continuous republishing of harmful variants. This not only pollutes the npm registry but also compromises the integrity of the development environment for users who unknowingly install these packages.

How To Fix

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

npm uninstall eka-serimuka65-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 measure, you can avoid using the 'eka-serimuka65-ruro' package and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to detect vulnerabilities in your dependencies.

Conclusion

The 'eka-serimuka65-ruro' package represents a significant threat to npm users due to its malicious intent to manipulate the npm registry. It is essential for developers to be vigilant, remove affected packages, and utilize tools like Vulert to safeguard their projects against such vulnerabilities.

See every vulnerability recorded for eka-serimuka65-ruro →

Share this vulnerability

FAQ

It is a malicious npm package associated with a token reward campaign that aims to manipulate the npm registry.

The vulnerability can lead to the installation of harmful packages that may compromise your project's integrity and security.

Immediately uninstall the package using 'npm uninstall eka-serimuka65-ruro' and review your other dependencies for potential vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without any signup.

How To Fix

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

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