Malicious Code Detected in dbk-breakpoints Package - Security Alert

dbk-breakpoints Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18098: Malicious code in dbk-breakpoints (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 dbk-breakpoints package is an npm library designed for managing breakpoints in debugging processes. It offers developers a streamlined way to handle breakpoints within their applications. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users who integrate it into their projects.

Vulnerability Detail

The vulnerability in the dbk-breakpoints package stems from the inclusion of malicious code that can compromise the integrity of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful effects on the system. The issue originated from version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall dbk-breakpoints

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, you can avoid using the dbk-breakpoints package entirely and implement your own breakpoint management solution or utilize alternative libraries that do not have known vulnerabilities.

Conclusion

The discovery of malicious code in the dbk-breakpoints package highlights the importance of vigilance in managing open-source dependencies. Users are urged to take immediate action to remove the affected package and consider alternatives to safeguard their applications.

See every vulnerability recorded for dbk-breakpoints →

Share this vulnerability

FAQ

dbk-breakpoints is an npm package used for managing breakpoints in debugging processes within applications.

The malicious code can lead to unauthorized access and data breaches, posing serious security risks to applications using this package.

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.

Remove the dbk-breakpoints package from your project and consider using a secure alternative. If a patched version is released, update the package accordingly.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to minimize the risk of vulnerabilities.

How To Fix

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

npm uninstall dbk-breakpoints

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