Malicious Code Detected in eksi-server: A Critical Vulnerability

eksi-server Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19298: Malicious code in eksi-server (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

eksi-server is an npm package designed for creating and managing server instances for the Eksi Sozluk platform, a popular Turkish online dictionary. It offers functionalities such as user authentication, data retrieval, and server management. However, recent findings have revealed that this package contains malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in eksi-server originates from the inclusion of malicious code within the package. This code can potentially compromise the security of applications using eksi-server, leading to unauthorized access, data breaches, or other malicious activities. The issue affects all versions starting from the initial release, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall eksi-server

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, consider removing the eksi-server package from your project until a secure version is released. You can uninstall it using the command: npm uninstall eksi-server.

Conclusion

The discovery of malicious code in the eksi-server package highlights the importance of vigilance in managing open-source dependencies. Users are urged to update or remove the package to mitigate risks associated with this vulnerability. Regular monitoring and updates are essential to maintaining application security.

See every vulnerability recorded for eksi-server →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential data breaches in applications utilizing the eksi-server package.

You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.

If immediate updates are not feasible, consider removing the package temporarily as a workaround until a secure version is available.

Currently, all versions of eksi-server are affected. It is crucial to monitor the package repository for any updates or patches.

Utilizing tools like Vulert can help you monitor and receive alerts for vulnerabilities in your open-source dependencies.

How To Fix

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

npm uninstall eksi-server

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