Critical Malicious Code Vulnerability in electhron Package

electhron Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19411: Malicious code in electhron (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 electhron package is a Node.js library designed to facilitate interactions with Electron applications. It provides developers with tools to enhance their applications' functionality and user experience. However, recent findings have revealed that this package contains malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the electhron package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may lead to unauthorized access, data breaches, or other harmful actions, potentially affecting the integrity and confidentiality of user data. 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 electhron

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, consider removing the electhron package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall electhron'. This will prevent any potential exploitation of the malicious code while you await a fix.

Conclusion

The electhron package has been identified as containing malicious code, posing a significant security risk to applications that utilize it. Users are advised to update or remove the package to safeguard their applications. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.

See every vulnerability recorded for electhron →

Share this vulnerability

FAQ

The electhron package is used to enhance the functionality of Electron applications, providing developers with tools for better application performance.

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

The malicious code can lead to unauthorized access, data breaches, and other harmful actions that compromise user data and application integrity.

Currently, there is no specific patch version mentioned. It is crucial to keep an eye on updates from the package maintainers.

If immediate updates are not possible, consider removing the electhron package from your project as a temporary workaround.

How To Fix

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

npm uninstall electhron

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