Malicious Code Detected in e3lectron Package - Security Alert

e3lectron Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19052: Malicious code in e3lectron (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 e3lectron package is a tool designed to facilitate the development of Electron applications, providing developers with essential functionalities to create cross-platform desktop applications using web technologies. 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 e3lectron package stems from the inclusion of malicious code that can compromise the integrity of applications built using this package. This malicious code could potentially lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and has been flagged as a critical security concern.

How To Fix

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

npm uninstall e3lectron

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 e3lectron package until a secure version is released. Alternatively, consider using other packages that provide similar functionalities without the associated risks.

Conclusion

The e3lectron package has been identified as containing malicious code, which poses serious security risks. Users are advised to update to the latest patched version or consider alternative solutions until the issue is resolved. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for e3lectron →

Share this vulnerability

FAQ

e3lectron is a package used for developing Electron applications, allowing developers to create desktop applications using web technologies.

The malicious code found in e3lectron can lead to unauthorized access and potential data breaches in applications built with this package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application using the Vulert playground at Vulert Scanner without any signup.

Yes, a patched version of the e3lectron package is available. You can update to the latest version using npm update e3lectron.

If immediate updates are not possible, consider using alternative packages or refrain from using e3lectron 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 e3lectron

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