Malicious Code Execution Vulnerability in debbug Package

debbug Updated 21 Oct 2026

Summary

20/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-18116: Malicious code in debbug (PyPI). Affects debbug versions 1.0.0. 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 debbug package, available on PyPI, is designed to assist developers in debugging Python applications. It offers various functionalities to streamline the debugging process. However, this package has been compromised, leading to a significant security vulnerability that allows the execution of malicious code during installation.

Vulnerability Detail

The vulnerability originates from a malicious version of the debbug package, specifically version 1.0.0, which downloads and executes malware from a remote server during installation. This poses severe risks, including unauthorized access to sensitive information and potential system compromise. The malicious code is executed without the user's consent, making it a classic case of typosquatting, where attackers exploit similar package names to deceive users.

How To Fix

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

pip uninstall debbug

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, consider using alternative debugging tools that are well-reviewed and have a strong security reputation. Avoid installing the debbug package until a safe version is released.

Conclusion

The debbug package has been compromised, leading to a serious vulnerability that allows for the execution of malicious code during installation. Users are advised to uninstall the affected version and monitor their systems closely. Utilizing tools like Vulert can help in identifying vulnerabilities in your applications.

See every vulnerability recorded for debbug →

Share this vulnerability

FAQ

The debbug package is a Python library designed to assist developers in debugging their applications more effectively.

The vulnerability allows malicious code to be executed on your system, potentially leading to data theft or system compromise.

If you have installed the debbug package, especially version 1.0.0, you should uninstall it immediately and monitor your system for any unusual activity.

You can use Vulert to monitor and alert in real-time for open-source vulnerabilities. Visit Vulert Scanner to check if your application is affected without requiring a signup.

A fix will depend on the package maintainers. Keep an eye on the official repository for updates or patches.

How To Fix

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

pip uninstall debbug

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