Malicious Code Detected in electrln Package - Security Risk Alert

electrln Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19428: Malicious code in electrln (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 electrln package is a Node.js library designed for specific functionalities within the npm ecosystem. It is utilized by developers for various applications, but recent findings have revealed that it contains malicious code, posing significant security risks to users and their projects. The presence of such code can lead to unauthorized access, data breaches, and other malicious activities.

Vulnerability Detail

The vulnerability in the electrln package stems from the inclusion of malicious code that can execute harmful operations within the user's environment. This code can compromise system integrity, leading to potential data theft or unauthorized actions. The issue originated from the package's initial release and affects all versions starting from 0. Users are at risk of exploitation if they have this package integrated into their applications.

How To Fix

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

npm uninstall electrln

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 electrln package and seek alternative libraries that provide similar functionalities without the associated risks. For example, consider using other well-reviewed npm packages that serve the same purpose.

Conclusion

The discovery of malicious code in the electrln package poses a serious threat to users and their applications. Immediate action is required to remove the package and safeguard against potential exploitation. Users are encouraged to monitor their dependencies and consider using tools like Vulert for ongoing vulnerability assessments.

See every vulnerability recorded for electrln →

Share this vulnerability

FAQ

The electrln package is a Node.js library used in various applications within the npm ecosystem.

The malicious code can execute harmful operations, potentially leading to data breaches and unauthorized access.

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

It is recommended to uninstall the electrln package immediately to protect your application from potential threats.

Yes, consider using other npm packages that provide similar functionalities without the security risks associated with electrln.

How To Fix

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

npm uninstall electrln

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