Critical Malicious Code Vulnerability in eklogger Package

eklogger Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19293: Malicious code in eklogger (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 eklogger package is an npm library designed for logging keystrokes and other user interactions in web applications. It is often used for debugging and monitoring purposes. However, due to its nature, it can be exploited if malicious code is introduced, posing significant security risks to applications that utilize it.

Vulnerability Detail

The eklogger package has been identified to contain malicious code that can compromise user data and security. This vulnerability originates from the package itself, which was found to have been tampered with, allowing attackers to execute harmful scripts. The ramifications include unauthorized data access, potential data breaches, and exploitation of user information, making it critical for developers to address this issue promptly.

How To Fix

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

npm uninstall eklogger

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 remove the eklogger package from your project until a secure version is available. Use the command: 'npm uninstall eklogger'. This will prevent any potential exploitation while you seek alternatives or wait for a fix.

Conclusion

The eklogger package has been found to contain malicious code, posing a significant security risk to applications that utilize it. Developers are urged to update the package to a secure version or remove it entirely until a fix is available. Regular monitoring for vulnerabilities is essential to maintain application security.

See every vulnerability recorded for eklogger →

Share this vulnerability

FAQ

The eklogger package is used for logging keystrokes and user interactions in web applications, primarily for debugging and monitoring.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without signup.

The malicious code can lead to unauthorized access to user data, data breaches, and exploitation of sensitive information, posing serious security threats.

Yes, you can temporarily uninstall the eklogger package from your project to prevent any potential exploitation until a secure version is released.

It is advisable to regularly check for vulnerabilities in your dependencies, ideally as part of your development workflow, to ensure your application remains secure.

How To Fix

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

npm uninstall eklogger

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