PAGES
← all tools
◆ Wireless & RF

apple-bleee

v0.1.5 open-source

Apple bleee is a set of experimental scripts that sniff Bluetooth BLE traffic to reveal information leaked by Apple devices.

source ↗ rss ↗ What is a cyber toolchain?

Summary

apple-bleee is an open-source command-line toolkit that sniffs Bluetooth Low Energy traffic from nearby Apple devices to extract status messages, phone number hashes, and AirDrop/AWDL identifiers, and it costs nothing to use. It runs as a set of Python scripts on Linux, tested on Kali, and needs a compatible Bluetooth adapter plus a WiFi card capable of monitor mode with frame injection for AWDL communication. It suits red teamers and wireless-security researchers doing reconnaissance or OSINTOSINTOpen-source intelligence, collecting and analyzing information from publicly available sources. Investigators use it to learn about people, infrastructure or threats. against Apple device proximity data rather than general network administrators. First committed in 2019 with 7 contributors and 3 tracked releases, it has seen no commits in the past year, so treat it as dormant rather than actively maintained.

Apple bleee is a set of experimental scripts that sniff Bluetooth BLE traffic to reveal information leaked by Apple devices.

How apple-bleee helps

Which Apple devices nearby are broadcasting status information over Bluetooth right now?

listens to BLE traffic in range and decodes the status messages Apple devices leak, showing device state without needing a pairing or connection

Can a phone number be recovered from a nearby Apple device's password-sharing request?

captures the first three bytes of the sha256 hash of the phone number from those requests and checks it against prepared hash tables to guess the original number

Who does a recovered phone number actually belong to, and where are they registered?

takes a phone number pulled from a hash match and queries lookup services and HLR data to return region information and subscriber details

What SSID is a nearby Apple device requesting or associated with?

pulls the SSID out of the BLE requests it sniffs, revealing network names tied to the device without joining that network

Can a device's advertised name be pulled without an active connection?

supports an active query mode against the BLE stack to fetch device names directly rather than waiting for one to appear passively

all 4 features, with the evidence for each →

Languages

Not documented

Features

4 capabilities · 2 backed by code, an API document or a real run

Built from apple-bleee's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What apple-bleee offers you

  • Command-line interface
All capabilities 4 capabilities
Decoding of proprietary Apple service messages shipped Decodes metadata from various Apple-specific communication protocols including Siri, Magic Switch, HomeKit, AirPrint, and AirPlay. 5 releases · first seen Jan 2020

release

Active BLE device discovery verified Discovers active Bluetooth Low Energy device names using gatttool. 1 release · 3 other sources · first seen Jan 2020

release

  • Adds -d/--action flag that automatically performs the GATT inquiry and retrieves the device name v0.1.5 · Jan 2020 · source · release history

docs

  • Sniffs Apple BLE traffic to extract device status, phone number hashes, and AirDrop data from nearby Apple devices.

command line

example

  • Show BLE sniffer help options python3 ble_read_state.py -h
Verbose output verified Provides verbose output mode for more detailed logging during tool operation. 1 release · 1 other source · first seen Oct 2019

release

  • Improves verbose mode with -v all to enable debug logging v0.1.5 · Jan 2020 · source · release history

command line

AirDrop data extraction shipped Extracts AirDrop information from nearby Apple devices. 1 other source

example

  • Show AirDrop leak script options python3 airdrop_leak.py -h

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for apple-bleee, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail apple-bleee puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

1 entry

  1. January 20201

    1 entry

    1. v0.1.5 Jan 17, 2020 · release notes

      Adds AirPrint, HomeKitHomeKitApple's smart-home platform and protocol that lets apps control lights, locks, sensors, and other accessories through a unified API, giving cyber tools a standard interface to audit or automate home devices., Hey Siri, AirPlay, and Magic Switch message decoding; adds -d/--action flag for auto device discovery.

      └──▷ GET THIS VERSION 
      $ git clone --branch v0.1.5 https://github.com/hexway/apple_bleee.git
# already have the repo? check out this version:
$ git checkout v0.1.5
      • Supports decoding of AirPrint messages
      • Supports decoding of HomeKit messages
      • Supports decoding of Hey Siri messages
      • Supports decoding of AirPlay messages
      • Supports decoding of Magic Switch messages
      +2 more show less
      • Adds -d/--action flag that automatically performs the GATT inquiry and retrieves the device name
      • Improves verbose mode with -v all to enable debug logging

      7 details in Everything

    Project health

    Issue, contributor and maintainer activity in hexway/apple_bleee, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 0 ±0 vs prior 12 months
    2. Maintainers 0 +0 joined · −0 left, last 12 months
    3. Bus factor 0 committers behind half the commits
    4. Community-filed not measured of issues opened, last 12 months
    5. Median time to close not measured issues closed, last 12 months
    6. Open backlog 22 of 36 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 22
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 2,186
    Issue themes, last 12 months not measured

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    compare.md

      Free the public facts, no sign-in Any paid plan all other sections Researcher & Business pricing history and category rank

      my-toolchain — 0 tools

        Betas, release candidates and previews. Turn it off to see final releases only. It also applies to changes you ask for over MCP when you're signed in.
        browse all tools → score card for your toolchain →
        cyber-toolchain / feedback

        Send us feedback