Malicious Code Execution Vulnerability in deebug Package

deebug Updated 21 Oct 2026

Summary

20/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-18117: Malicious code in deebug (PyPI). Affects deebug 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 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 deebug package, available on the Python Package Index (PyPI), is designed for debugging Python applications. It is intended to assist developers in identifying and resolving issues within their code. 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 deebug package, specifically version 1.0.0, which was uploaded by a user identified as kam193. Upon installation, this package downloads and executes malware from a remote server, posing a severe risk to users' systems. The malicious behavior includes downloading an executable from the domain c2-worker.crawlnet-claim.workers.dev, which can lead to unauthorized access and data theft.

How To Fix

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

pip uninstall deebug

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 workaround, users can consider using alternative debugging packages such as 'pdb' or 'pdb++' that do not have known vulnerabilities. Additionally, ensure that your environment is secure and monitor for any unusual activity after the installation of any package.

Conclusion

The deebug 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 package immediately and consider alternative debugging tools to ensure their systems remain secure.

See every vulnerability recorded for deebug →

Share this vulnerability

FAQ

deebug is a Python package designed to assist developers in debugging their applications by providing tools and functionalities to identify and resolve issues.

The vulnerability allows the installation of malicious code that can execute harmful actions on your system, potentially leading to data theft or unauthorized access.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Immediately uninstall the deebug package using 'pip uninstall deebug' and consider using alternative debugging tools.

Currently, there is no patched version available for the deebug package. It is recommended to avoid using it altogether.

How To Fix

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

pip uninstall deebug

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