Malicious Code Detected in elecyron Package - Security Alert

elecyron Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19472: Malicious code in elecyron (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 elecyron package is a Node.js library designed for various functionalities within JavaScript applications. It is widely used in the npm ecosystem for its ease of integration and utility. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the elecyron package. This code can potentially compromise the integrity of applications using the package, leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall elecyron

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 remove the elecyron package from their project until a secure version is released. This can be done using the command: 'npm uninstall elecyron'. Alternatively, consider using an alternative package that offers similar functionality without the security risks.

Conclusion

The elecyron package has been identified as containing malicious code, posing a significant threat to applications that utilize it. Immediate action is required to update or remove the package to mitigate potential risks. Users are encouraged to leverage tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for elecyron →

Share this vulnerability

FAQ

The elecyron package is a Node.js library used in JavaScript applications for various functionalities.

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

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

As a workaround, consider uninstalling the elecyron package or using an alternative package until a secure version is available.

Utilize tools like Vulert to monitor your package-lock.json for real-time alerts on open-source vulnerabilities.

How To Fix

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

npm uninstall elecyron

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