Malicious Code Detected in el4ctron Package - Security Alert

el4ctron Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19302: Malicious code in el4ctron (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The el4ctron package is a Node.js library designed for building cross-platform desktop applications using web technologies. It is widely used for its ease of integration with Electron, allowing developers to create rich user interfaces. However, the package has been identified to contain malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the el4ctron package originates from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may allow unauthorized access to sensitive data, execute arbitrary commands, or facilitate other malicious activities. The presence of such vulnerabilities can lead to severe ramifications, including data breaches, loss of user trust, and potential legal implications for developers and organizations.

How To Fix

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

npm uninstall el4ctron

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

If an immediate update is not feasible, consider removing the el4ctron package from your project until a secure version is released. You can do this by executing: npm uninstall el4ctron.

Conclusion

The el4ctron package has been identified to contain malicious code, posing significant security risks. It is crucial for developers to update to a patched version or remove the package until a secure release is available. Utilizing tools like Vulert can help in monitoring vulnerabilities effectively.

See every vulnerability recorded for el4ctron →

Share this vulnerability

FAQ

el4ctron is a Node.js library used for building cross-platform desktop applications with web technologies.

The malicious code can potentially allow unauthorized access to sensitive data and execute arbitrary commands.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Consider removing the el4ctron package from your project until a secure version is available.

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software.

How To Fix

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

npm uninstall el4ctron

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