Critical Malicious Code Vulnerability in electronm Package

electronm Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19459: Malicious code in electronm (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 electronm package is a Node.js library that facilitates the development of cross-platform desktop applications using web technologies. It is designed to streamline the integration of web-based functionalities into native applications. However, this package has been identified to contain malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the electronm package arises from the presence 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 within the affected systems. The malicious nature of this vulnerability was discovered by Amazon Inspector, highlighting the importance of scrutinizing third-party packages for security risks.

How To Fix

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

npm uninstall electronm

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 electronm package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall electronm'. This will help prevent any potential exploitation of the malicious code present in the package.

Conclusion

The electronm package has been identified to contain malicious code, posing a significant security risk to applications that utilize it. Users are advised to update the package as soon as a patched version is available or to remove it from their projects temporarily. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for electronm →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential data breaches in applications that utilize the electronm package.

You can use Vulert to monitor and alert in real-time for open-source vulnerabilities. Check your application by visiting the Vulert playground at Vulert Scanner without any signup.

If an immediate update is not possible, consider removing the electronm package from your project as a temporary workaround.

The vulnerability was discovered by Amazon Inspector, a tool designed to identify security risks in software packages.

As of now, a patched version has not been specified. It is essential to monitor the package repository for updates.

How To Fix

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

npm uninstall electronm

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