Malicious Code Detected in elewctron Package - Security Alert

elewctron Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19524: Malicious code in elewctron (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 elewctron package is a Node.js library that is designed to facilitate the development of desktop applications using web technologies. It is commonly used for creating cross-platform applications. However, the package has been identified to contain malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the elewctron 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, and potential exploitation of the affected systems. Users of the elewctron package should be aware of the risks associated with using this compromised library.

How To Fix

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

npm uninstall elewctron

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 workaround, you can avoid using the elewctron package altogether and explore alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your application for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for any security issues.

Conclusion

The elewctron package has been found to contain malicious code, posing serious security risks to applications that utilize it. Users are advised to remove the package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed and proactive is crucial in maintaining application security.

See every vulnerability recorded for elewctron →

Share this vulnerability

FAQ

elewctron is a Node.js library used for building desktop applications with web technologies.

The malicious code was identified through security audits and reports from security researchers.

Using the elewctron package can lead to unauthorized access, data breaches, and exploitation of your applications.

You can use Vulert's playground to analyze your package-lock.json file for vulnerabilities without any signup.

Remove the elewctron package from your project and replace it with a secure alternative immediately.

How To Fix

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

npm uninstall elewctron

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