Malicious Code Detected in eoectron Package - Security Alert

eoectron Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19689: Malicious code in eoectron (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 eoectron package is a Node.js library designed for building cross-platform desktop applications. It leverages web technologies to create native applications, making it popular among developers looking to streamline their development process. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the eoectron package stems from the inclusion of malicious code that can compromise the integrity of applications utilizing this library. This code may allow unauthorized access to sensitive data, facilitate remote code execution, or lead to other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall eoectron

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, users can avoid using the eoectron package until a secure version is released. Alternatively, consider using other similar packages that do not have known vulnerabilities.

Conclusion

The discovery of malicious code in the eoectron package highlights the importance of maintaining secure dependencies in software development. Users are urged to update their packages promptly and consider utilizing tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for eoectron →

Share this vulnerability

FAQ

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

The malicious code can compromise application integrity, allowing unauthorized access to sensitive data and potentially enabling remote code execution.

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

As a workaround, consider avoiding the use of the eoectron package until a secure version is available or switch to alternative packages.

Utilize tools like Vulert to monitor your dependencies in real-time for any open-source vulnerabilities.

How To Fix

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

npm uninstall eoectron

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