Malicious Code Detected in bdfg43 Package - Immediate Action Required

bdfg43 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15548: Malicious code in bdfg43 (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 bdfg43 package is an npm library that serves various functionalities within JavaScript applications. It is designed to enhance development processes by providing reusable code components. However, the package has been identified to contain malicious code, posing significant security risks to applications that utilize it. Users of this package should be aware of its potential vulnerabilities and take necessary precautions.

Vulnerability Detail

The vulnerability in the bdfg43 package arises 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 within the affected systems. The malicious nature of this vulnerability was confirmed through security assessments and has been documented in the Open Source Vulnerability database.

How To Fix

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

npm uninstall bdfg43

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, consider removing the bdfg43 package from your project until a secure version is released. You can do this by executing: 'npm uninstall bdfg43'. This will prevent any potential exploitation of the malicious code while you seek alternatives or wait for a fix.

Conclusion

The discovery of malicious code in the bdfg43 package highlights the importance of vigilance in managing open-source dependencies. Users must take immediate action to update or remove the affected package to safeguard their applications from potential threats.

See every vulnerability recorded for bdfg43 →

Share this vulnerability

FAQ

bdfg43 is an npm package that provides various functionalities for JavaScript applications, but it has been found to contain malicious code.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

If you are using bdfg43, you should immediately update the package or remove it from your project to mitigate security risks.

Check the npm repository for bdfg43 to see if a patched version has been released. If so, update your package using 'npm update bdfg43'.

Using a package with malicious code can lead to unauthorized access, data breaches, and potentially severe damage to your application and its users.

How To Fix

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

npm uninstall bdfg43

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