Malicious Code Detected in edlectron Package - Security Alert

edlectron Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19222: Malicious code in edlectron (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 edlectron package is a tool designed for building cross-platform desktop applications using web technologies. It allows developers to create applications that run on Windows, macOS, and Linux. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the edlectron package stems from the inclusion of malicious code that can compromise the security of applications built using this package. This code may allow unauthorized access to sensitive data, lead to data breaches, or enable remote code execution. The issue was introduced in version 0 and affects all subsequent versions, 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 edlectron

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 are advised to remove the edlectron package from their projects until a secure version is released. You can do this by executing the command: 'npm uninstall edlectron'. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the edlectron package highlights the importance of maintaining secure coding practices and regularly monitoring dependencies for vulnerabilities. Users must take immediate action to protect their applications and data by updating or removing the affected package.

See every vulnerability recorded for edlectron →

Share this vulnerability

FAQ

The edlectron package is used for building cross-platform desktop applications using web technologies.

The malicious code can compromise application security, potentially leading to unauthorized access and data breaches.

You can use Vulert to monitor and alert for vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected.

Currently, there is no patched version available. Users should monitor the official repository for updates.

If you cannot update the package, it is recommended to uninstall edlectron and consider using alternative packages until a secure version is released.

How To Fix

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

npm uninstall edlectron

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