Malicious Code Detected in bdce3 Package - Security Alert

bdce3 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15547: Malicious code in bdce3 (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 bdce3 package is an npm module that is utilized for various functionalities in JavaScript applications. It is designed to provide specific features that enhance the development process. However, this package has been identified to contain malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the bdce3 package stems from the inclusion of malicious code that can compromise the security of applications using this package. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall bdce3

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 bdce3 package in your application until a secure version is released. Review your codebase to identify any dependencies on bdce3 and consider refactoring your code to eliminate its usage.

Conclusion

The bdce3 package has been identified as containing malicious code, which poses a significant security risk to applications that utilize it. It is essential to remove this package and monitor for updates or patches. Utilizing tools like Vulert can help keep your applications secure by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for bdce3 →

Share this vulnerability

FAQ

bdce3 is an npm package used in JavaScript applications to provide specific functionalities. However, it has been flagged for containing malicious code.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can help you identify if your application is affected by this vulnerability.

If you are using bdce3, it is recommended to remove it from your project and look for a secure alternative. Keep an eye on the package repository for any patches or updates.

Yes, you can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any code access or installation.

Using bdce3 can lead to serious security risks, including unauthorized access to sensitive data, data breaches, and potential exploitation of your application.

How To Fix

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

npm uninstall bdce3

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