license: apache-2.0
pretty_name: Wireless Vendor Identifier Metadata
tags:
- bluetooth
- ble
- wireless
- oui
- cybersecurity
- metadata
- vendor-identifiers
- tabular
size_categories:
- 1K<n<10K
configs:
- config_name: vendor_identifiers
data_files:
- split: train
path: data/vendor_identifiers.csv
- config_name: bluetooth_assigned_numbers
data_files:
- split: train
path: data/bluetooth_assigned_numbers.csv
- config_name: vendor_summary
data_files:
- split: train
path: data/vendor_summary.csv
- config_name: ecosystem_profiles
data_files:
- split: train
path: data/ecosystem_profiles.csv
- config_name: source_manifest
data_files:
- split: train
path: data/source_manifest.csv
Wireless Vendor Identifier Metadata
This dataset contains public wireless and Bluetooth metadata relevant to BLE research. It is designed for defensive analysis, asset classification, literature support, and reproducible metadata lookup. The dataset is split into multiple tables so it is not just an OUI mirror.
It deliberately excludes complete BLE advertisement payloads, packet templates, radio timing recipes, device captures, effectiveness labels, and any instructions for impersonation or nuisance testing.
Dataset Contents
data/vendor_identifiers.csv: normalized identifier records from public vendor registries.data/bluetooth_assigned_numbers.csv: selected Bluetooth SIG assigned numbers useful for interpreting BLE metadata, including AD types, GAP appearances, GATT services, characteristics, descriptors, declarations, protocol UUIDs, service-class UUIDs, and unit UUIDs.data/vendor_summary.csv: per-vendor counts by identifier namespace.data/ecosystem_profiles.csv: curated ecosystem context for Apple, Samsung, Google/Android, Huawei, Xiaomi, OPPO/OnePlus/realme, vivo, Sony, LG, Motorola/Lenovo, Microsoft, Amazon, and Meta.data/vendors.csv: vendor group labels and ecosystem tags used during curation.data/source_manifest.csv: source URLs, snapshot hashes, and row counts.schema/vendor_identifiers.schema.json: vendor identifier schema.schema/bluetooth_assigned_numbers.schema.json: assigned-number schema.
Current vendor identifier records: 6213.
Current Bluetooth assigned-number records: 1227.
Snapshot date: 2026-05-25.
Intended Use
Appropriate uses include:
- mapping observed public identifiers to likely vendor families;
- interpreting BLE metadata fields such as AD Type, Appearance, GATT Service, GATT Characteristic, and Descriptor values;
- building defensive BLE inventory or wireless metadata analysis tools;
- supporting academic writing about BLE discovery, manufacturer identifiers, and vendor ecosystems;
- training or evaluating classifiers on benign public registry metadata.
Do not use this dataset to generate, optimize, or test spoofed advertisements against devices or people without explicit authorization. Do not combine it with payload templates, timing profiles, or captured device identifiers to conduct impersonation, spam, harassment, or availability attacks.
Sources
- IEEE Registration Authority OUI CSV:
https://standards-oui.ieee.org/oui/oui.csv - Bluetooth SIG Assigned Numbers YAML repository:
https://www.bluetooth.com/specifications/assigned-numbers/
The curated dataset is provided for research convenience. Source registry terms remain with the respective source authorities; verify current data against the official registries before operational use.
License
The dataset packaging, schemas, curation scripts, and original descriptive metadata in this repository are released under the Apache License 2.0.
The underlying public registry data is derived from IEEE Registration Authority and Bluetooth SIG sources. Those source registry terms, notices, trademarks, and attribution requirements remain with the respective source authorities. This dataset does not grant rights beyond the public metadata curation and packaging provided here.
Data Fields
See the files in schema/ for column-level details.
Safety Boundary
This dataset is public identifier metadata only. It does not contain:
- complete BLE Manufacturer Specific Data values;
- Apple, Samsung, Android, or other proximity-pairing payloads;
- randomized device addresses, captured MAC addresses, RPAs, RSSI, timestamps, or location data;
- tested trigger rates, success labels, or spam-tuning parameters.
Known Limitations
- Vendor grouping is keyword-based and intended as a research convenience, not an authoritative corporate ownership graph.
- IEEE OUI assignments are numerous, so the vendor identifier table is still OUI-heavy. The separate Bluetooth assigned-number and ecosystem tables are included to make the dataset useful beyond OUI lookup.
- Identifier ownership does not prove that a specific nearby radio device is made by that vendor.
- Bluetooth assigned numbers describe public metadata fields; they do not imply support for any proprietary proximity-pairing protocol.
Citation
If you use this dataset, cite the Hugging Face dataset repository and the underlying IEEE and Bluetooth SIG registries listed above.