Critical Malicious Code Vulnerability in eldctron Package

eldctron Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19316: Malicious code in eldctron (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The eldctron package is a Node.js library designed to facilitate the development of desktop applications using web technologies. It combines the capabilities of Electron and other libraries to provide developers with tools to create cross-platform applications. However, the package has been identified to contain malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the eldctron package originates from the inclusion of malicious code that can compromise the security of applications utilizing this package. This malicious code can lead to unauthorized access, data breaches, or even complete system takeover. The vulnerability affects all versions starting from 0, making it critical for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall eldctron

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, users can avoid using the eldctron package until a secure version is released. Alternatively, consider using other similar packages that do not have known vulnerabilities.

Conclusion

The eldctron package has been identified to contain malicious code, posing significant risks to users. It is crucial for developers to take immediate action by updating the package or finding alternatives. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.

See every vulnerability recorded for eldctron →

Share this vulnerability

FAQ

The eldctron package is used for developing desktop applications using web technologies, combining Electron with other libraries.

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

If you are using eldctron, you should immediately update to a patched version once it is released or consider removing the package until it is secured.

Using a package with malicious code can lead to unauthorized access to your system, data breaches, and potential exploitation of your applications.

Regularly monitor your dependencies using tools like Vulert, and keep your packages updated to the latest secure versions to minimize risks.

How To Fix

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

npm uninstall eldctron

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