Critical Malicious Code Vulnerability in electroln Package

electroln Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19442: Malicious code in electroln (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 electroln package is an npm library designed for facilitating electronic payments and transactions. It offers various functionalities that allow developers to integrate payment processing into their applications seamlessly. However, the package has been found to contain malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the electroln package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful actions that can affect both developers and end-users. The issue was introduced in version 0 and persists in all subsequent versions, making it critical for users to address this vulnerability immediately.

How To Fix

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

npm uninstall electroln

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 avoid using the electroln package altogether and look for alternative libraries that provide similar functionalities without the associated risks. Additionally, ensure that your application is regularly monitored for vulnerabilities using tools like Vulert.

Conclusion

The electroln package has been identified as containing malicious code, which poses significant security risks to applications that utilize it. Users are strongly advised to remove the package and monitor their applications for vulnerabilities using tools like Vulert. Staying informed and proactive is essential to maintaining application security.

See every vulnerability recorded for electroln →

Share this vulnerability

FAQ

The electroln package is an npm library used for electronic payment processing in applications.

The malicious code can lead to unauthorized access and potential data breaches, posing serious security risks.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check your application without any signup.

Currently, there is no patched version available for the electroln package. Users are advised to remove it from their projects.

You should remove the electroln package immediately and consider using a secure alternative for payment processing.

How To Fix

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

npm uninstall electroln

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