HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
seemoo-lab
internalblue
Python2020–2024
seemoo-lab / internalblue

internalblue

Bluetooth experimentation framework for Broadcom and Cypress chips.

2Distinct people
3Mentions
0Explicit recommenders
793GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Bluetooth experimentation framework for Broadcom and Cypress chips.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year3 dated mentions

Observed mentions: 2020-11-12 20:17:13 UTC to 2024-05-13 06:03:00 UTC.

012020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

3 sources
Regarding firmware patching, look at InternalBlue [1]. I guess they did it for one IC, but obviously can't do it at will for just any IC and instead hand wave "it can be done". Overall I don't think it's impossible: Someone stated it would be unidirectional, and the bitrate was not given (read: could even be minutes per bit for all we know). But yeah, I'm sceptical, too. A gateway would have made more sense to me, because it does not require firmware-level cooperation with chip set manufacturers and you can reuse existing space networks. Especially since they're not aiming to add the feature into future ICs (which could have driven sales across the whole industry), but backport it instead, competing with the manufacturers and voiding existing FCC et al. certification. [1] https://github.com/seemoo-lab/internalblue
In Tech startup connects to two satellites in orbit from Earth via Bluetooth
I wonder how they deal with the channel hopping? I remember BT "Classic" derives the hoping sequence from the encryption key. Not sure if that changed significantly for BLE? So either they establish normal connections between relays and victims (meaning two keys, one between each relay and each victim), and then forward data coming out of the Link Layer between the attacker devices - or they need to sniff the whole spectrum in case there is just one key between car and fob. Last time I checked, sniffing the full spectrum of BT required three SDRs, meaning six in total; making this attack rather expensive to pull off (no problem for professional thieves though, I guess). OTOH if they can use any BT stack (or manipulate it with e.g. InternalBlue[1]), potential carjackers just need two Android Phones and good WiFi :( [1] InternalBlue: https:
Read the rest
//github.com/seemoo-lab/internalblue //edit: I think letting the phone do some sanity checking is already a good idea. There are some indicators that can be used to make this much harder (though not impossible), and which are generally available right now (that is, without additional hardware). The two most obvious: Do the GPS locations match up (prevent theft while at other end of a mall)? Did the acceleration sensors indicate that the phone might have been moved closer to the car (prevent theft while sleeping with phone on the nightstand)?
In Bluetooth relay attacks allow Tesla Model 3 / Y to be unlocked and driven away

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.