Repository navigation
Troubleshooting
Recent Debian/Ubuntu/Fedora block global pip installs. Use a venv:
python3 -m venv .venv && source .venv/bin/activate
pip install -e .…or pass --break-system-packages to pip (also handled automatically by install.sh).
You need PyBluez/pybluez2 for Classic-BT modules:
pip install pybluez2Requires libbluetooth-dev (Debian/Ubuntu) or bluez-libs-devel (Fedora). On macOS, this won't install — Classic BT isn't supported on macOS; only BLE via bleak.
Raw HCI access needs CAP_NET_RAW or root:
sudo python3 bluesploit.py
# or grant the capability once:
sudo setcap 'cap_net_raw,cap_net_admin+eip' "$(readlink -f $(which python3))"rfkill list # ensure unblocked
sudo rfkill unblock bluetooth
sudo systemctl start bluetooth
hciconfig # should now show hci0
sudo hciconfig hci0 upGrant Bluetooth permission to your Terminal app: System Settings → Privacy & Security → Bluetooth → enable Terminal/iTerm.
Either your adapter is rfkill-soft-blocked, or another process owns the HCI:
sudo systemctl stop bluetooth # release BlueZ's grip for raw modules
sudo hciconfig hci0 down && sudo hciconfig hci0 upAfter raw-HCI work, restart bluetoothd to restore normal pairing.
You're missing system headers. Install per-distro packages from Installation, then retry. On older Python (<3.8) it won't compile — upgrade Python.
WSL doesn't expose the host radio. Either:
- Use a USB BT dongle via
usbipd-winpassthrough, or - Run BlueSploit on bare Linux.
bsploit > use auxiliary/hw_detect
bsploit (auxiliary/hw_detect) > run
Check the output. If a backend is missing, see the matching section in Hardware Setup.
Open an issue: https://github.com/v33ru/bluesploit/issues with:
- OS + version
python3 --versionpip list | grep -E 'bleak|pybluez|bluepy|btlejack|scapy'-
hciconfigoutput - The full traceback
BlueSploit · MIT License · For authorized security research only · Issues · Disclaimer
Getting Started
Modules
Hardware & Internals
Help