Malicious Code Detected in Electrton Package - MAL-2025-19466

electrton Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19466: Malicious code in electrton (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

Electrton is an npm package designed for building desktop applications using web technologies. It allows developers to create cross-platform applications with a rich user interface. However, recent findings have revealed that the package contains malicious code, posing a significant risk to users and their applications.

Vulnerability Detail

The vulnerability in the electrton package originates from the inclusion of malicious code that can compromise the security of applications using this package. This code may lead to unauthorized access, data breaches, or other harmful actions that can affect both developers and end-users. The malicious nature of the code makes it imperative 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 electrton

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, users can remove the electrton package from their project until a secure version is released. This can be done by executing the command: 'npm uninstall electrton'. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the electrton package highlights the importance of maintaining secure dependencies in software development. Users are urged to take immediate action by updating or removing the package to protect their applications from potential threats.

See every vulnerability recorded for electrton →

Share this vulnerability

FAQ

Electrton is used for building cross-platform desktop applications using web technologies.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring signup.

You should immediately update the electrton package or uninstall it until a secure version is available.

Using the electrton package with malicious code can lead to unauthorized access, data breaches, and other harmful actions affecting your application and its users.

Yes, Vulert provides a service to monitor your package-lock.json for vulnerabilities in real-time, ensuring you are alerted to any issues as they arise.

How To Fix

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

npm uninstall electrton

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