HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
auracast-research
race-toolkit
Python2025–2026
auracast-research / race-toolkit

race-toolkit

Communicate with Airoha-based Bluetooth devices using the RACE protocol via Bluetooth and USB.

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

What to know before exploring

What it is

Communicate with Airoha-based Bluetooth devices using the RACE protocol via Bluetooth and USB.

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, 5:04:57 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 6-hour interval3 dated mentions

Observed mentions: 2025-12-27 22:58:34 UTC to 2026-01-01 15:39:16 UTC.

0122025-12-27 18:00:00 UTC to 2025-12-28 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsDec 27, 18:002025-12-28 00:00:00 UTC to 2025-12-28 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-28 06:00:00 UTC to 2025-12-28 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-28 12:00:00 UTC to 2025-12-28 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-28 18:00:00 UTC to 2025-12-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-29 00:00:00 UTC to 2025-12-29 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-29 06:00:00 UTC to 2025-12-29 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-29 12:00:00 UTC to 2025-12-29 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-29 18:00:00 UTC to 2025-12-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-30 00:00:00 UTC to 2025-12-30 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsDec 30, 00:002025-12-30 06:00:00 UTC to 2025-12-30 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-30 12:00:00 UTC to 2025-12-30 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-30 18:00:00 UTC to 2025-12-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-31 00:00:00 UTC to 2025-12-31 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-31 06:00:00 UTC to 2025-12-31 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-31 12:00:00 UTC to 2025-12-31 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-31 18:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2026-01-01 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 06:00:00 UTC to 2026-01-01 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 12:00:00 UTC to 2026-01-01 18:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsJan 1, 12:00

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
Dec 27, 18:002025-12-27 18:00:00 UTC2025-12-28 00:00:00 UTC110
Dec 28, 00:002025-12-28 00:00:00 UTC2025-12-28 06:00:00 UTC000
Dec 28, 06:002025-12-28 06:00:00 UTC2025-12-28 12:00:00 UTC000
Dec 28, 12:002025-12-28 12:00:00 UTC2025-12-28 18:00:00 UTC000
Dec 28, 18:002025-12-28 18:00:00 UTC2025-12-29 00:00:00 UTC000
Dec 29, 00:002025-12-29 00:00:00 UTC2025-12-29 06:00:00 UTC000
Dec 29, 06:002025-12-29 06:00:00 UTC2025-12-29 12:00:00 UTC000
Dec 29, 12:002025-12-29 12:00:00 UTC2025-12-29 18:00:00 UTC000
Dec 29, 18:002025-12-29 18:00:00 UTC2025-12-30 00:00:00 UTC000
Dec 30, 00:002025-12-30 00:00:00 UTC2025-12-30 06:00:00 UTC000
Dec 30, 06:002025-12-30 06:00:00 UTC2025-12-30 12:00:00 UTC000
Dec 30, 12:002025-12-30 12:00:00 UTC2025-12-30 18:00:00 UTC000
Dec 30, 18:002025-12-30 18:00:00 UTC2025-12-31 00:00:00 UTC000
Dec 31, 00:002025-12-31 00:00:00 UTC2025-12-31 06:00:00 UTC000
Dec 31, 06:002025-12-31 06:00:00 UTC2025-12-31 12:00:00 UTC000
Dec 31, 12:002025-12-31 12:00:00 UTC2025-12-31 18:00:00 UTC000
Dec 31, 18:002025-12-31 18:00:00 UTC2026-01-01 00:00:00 UTC000
Jan 1, 00:002026-01-01 00:00:00 UTC2026-01-01 06:00:00 UTC000
Jan 1, 06:002026-01-01 06:00:00 UTC2026-01-01 12:00:00 UTC000
Jan 1, 12:002026-01-01 12:00:00 UTC2026-01-01 18:00:00 UTC202

What Hacker News says

3 sources
Glad this submission is finally receiving upvotes. This was just shown at the 39C3 in Hamburg, few days back. Common (unpached) Bluetooth headsets using Airoha's SoCs can be completely taken over by any unauthenticated bystander with a Linux laptop. (CVE-2025-20700, CVE-2025-20701, CVE-2025-20702) This includes firmware dumps, user preferences, Bluetooth Classic session keys, current playing track, ... > Examples of affected vendors and devices are Sony (e.g., WH1000-XM5, WH1000-XM6, WF-1000XM5), Marshall (e.g. Major V, Minor IV), Beyerdynamic (e.g. AMIRON 300), or Jabra (e.g. Elite 8 Active). Most vendors gave the security researchers either silent treatment or were slow, even after Airoha published fixes. Jabra was one of the positive outlier, Sony unfortunately negatively. What is exciting, even though the flaws are awful, that it is u
Read the rest
nlikely for current generation of those Airoha bluetooth headsets to change away from Aiorha's Bluetooth LE "RACE" protocol. This means there is great opportunity for Linux users to control their Bluetooth headsets, which for example is quite nice in an office setting to toggle "hearthrough" when toggling volume "mute" on your machine. RACE Reverse Engineered - CLI Tool: https://github.com/auracast-research/race-toolkit I feel like this should receive state-level attention, the remote audio surveillance of any headset can be a major threat. I wonder what the policies in countries official buildings are when it comes to Bluetooth audio devices, considering that Jabra is a major brand for conference speakers, I'd assume some actual espionage threats.
In Bluetooth Headphone Jacking: A Key to Your Phone [video]

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.