Malicious Code Detected in electrobn Package - Security Alert

electrobn Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19435: Malicious code in electrobn (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The electrobn package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for its ease of integration and utility in various projects. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the electrobn package stems from the inclusion of malicious code that can compromise the security of applications using it. This code can lead to unauthorized access, data breaches, and potential exploitation of user systems. The malicious nature of this code was identified by security researchers, emphasizing the need for immediate action to mitigate risks associated with its use.

How To Fix

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

npm uninstall electrobn

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, you can avoid using the electrobn package in your project until a secure version is released. Consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The electrobn package has been identified as containing malicious code, which poses serious security threats to applications. It is crucial for developers to take immediate action by removing the package and monitoring their projects for vulnerabilities. Utilizing tools like Vulert can enhance security measures and ensure safer development practices.

See every vulnerability recorded for electrobn →

Share this vulnerability

FAQ

The electrobn package is an npm library used in JavaScript applications for various functionalities.

The malicious code can lead to unauthorized access and exploitation of user systems, posing significant security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

You should remove the electrobn package from your project and look for alternative packages until a secure version is released.

Yes, Vulert can help you monitor your dependencies for vulnerabilities using just the package-lock.json file, without requiring access to your code.

How To Fix

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

npm uninstall electrobn

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