PhyPlus — 10 prefixes (MA-L), two registry entities

PhyPlus is a Shanghai-based fabless semiconductor vendor whose OUI footprint spans two distinct IEEE registry entities: "Phyplus Microelectronics Limited" and "Phyplus Technology (Shanghai) Co., Ltd" — five MA-L blocks each, ten in total, all carrying Shanghai, CN addresses. The two names are the same corporate group, so consolidating them under a single vendor entry is more useful than two near-identical pages. PhyPlus does not ship network infrastructure; its business is Bluetooth Low Energy (BLE) System-on-Chip silicon (the PHY62 series — PHY6202, PHY6212, PHY6222, PHY6230, PHY6252), so a PhyPlus OUI on a network reliably indicates a consumer or industrial IoT *end node* rather than a switch, router, or AP. Devices built on these SoCs include smart-home gear (lighting, plugs, sensors), TWS earbuds and other hearables, wearables, BLE-mesh nodes, beacons, and health devices; the PHY62 line also supports Zigbee/Thread/Matter, so a PhyPlus-prefixed device may present as BLE-only or dual-protocol. The chips are a supported hardware target on the Tuya IoT platform, which corroborates the smart-home device profile — a PhyPlus OUI may well sit on a network alongside Tuya-cloud devices. Two operational caveats apply. First, registration dates: IEEE publishes none, and the per-vendor "date registered" values shown on third-party lookup tools (e.g. an earliest 2019-07-02 on maclookup.app) are database artifacts, not IEEE facts — they must not be surfaced as IEEE registration dates. Second, security: as of 2026-06-15 no PhyPlus-specific CVE appears in NVD or the CISA KEV catalog; the one BLE CVE that surfaced in search (CVE-2025-54646) resolves to a Huawei product, not PhyPlus. General BLE risks (device fingerprinting, proximity tracking, SoC-class bugs like the BLEEDINGBIT family that hit other vendors) apply to any BLE node on a scanned network, but none name PhyPlus; the real security posture of a given device depends on the OEM's firmware, not the chip vendor alone.

IEEE assignment

10 MA-L prefixes across two entities — "Phyplus Microelectronics Limited" (5) and "Phyplus Technology (Shanghai) Co., Ltd" (5), both Shanghai, CN [Confirmed] — IEEE MA-L (oui.csv)

Registry / block size

MA-L (24-bit OUI); 10 IEEE prefixes total. NOTE: IEEE's public OUI data publishes NO assignment/registration date (oui.csv columns are only Registry, Assignment, Organization Name, Organization Address); any "date registered" on third-party tools (e.g. maclookup.app's earliest 2019-07-02) is a database artifact, not an IEEE fact. [Confirmed] — IEEE MA-L; maclookup.app

Entity A — Phyplus Microelectronics Limited

OUIs 40:B7:FC, E4:98:BB, 34:EC:B6, E0:68:EE, 80:AC:C8; registry address "304 Building 1, No.608 Sheng Xia Road, Shanghai, CN 200000" [Confirmed] — IEEE MA-L (oui.csv), corroborated by maclookup.app

Entity B — Phyplus Technology (Shanghai) Co., Ltd

OUIs DC:9B:95, A4:6D:33, BC:14:69, E8:B5:27, 60:D8:77; registry address "3th Floor, Building 23, 676 Wuxing Road, Pudong New District, Shanghai, CN 201204" [Confirmed] — IEEE MA-L (oui.csv)

Additional prefix (web-only, single-source)

B0:EB:AA listed under "Phyplus Microelectronics Limited" on maclookup.app but NOT present in the local IEEE oui.csv snapshot used here — treat as a possible newer/registry-lag block, not yet confirmed against IEEE [Likely] — https://maclookup.app/vendors/phyplus-microelectronics-limited

HQ / country

Shanghai, China (Pudong New Area); English portal en.phyplusinc.com [Confirmed] — IEEE MA-L; http://en.phyplusinc.com/

Company status

active [Confirmed] — http://en.phyplusinc.com/about_1.html

Device types

BLE SoC silicon (PHY62 series) embedded in IoT end nodes — smart home (lighting, plugs, sensors), TWS earbuds/hearables, wearables, BLE-mesh nodes, beacons, health/medical, industrial IoT modules; PHY62 also supports Zigbee/Thread/Matter [Confirmed] — http://en.phyplusinc.com/product/1.html; http://en.phyplusinc.com/about_1.html

Notable products

PHY62 series — PHY6202, PHY6212, PHY6222, PHY6230, PHY6252 [Confirmed] — http://en.phyplusinc.com/product/1.html

Platform / certifications

PHY6222 is a supported hardware target on the Tuya IoT platform; PHY62 series self-reported to hold Apple MFi, Bluetooth SIG (BLE 5.2 + Mesh), Zigbee CSA, and Tencent Cloud certifications [Likely — Tuya support Confirmed via Tuya docs; certification list is vendor-stated] — https://developer.tuya.com/en/docs/iot-device-dev/bluetooth_platform_ble_phy6222?id=Kcnreamkf9r1a; http://en.phyplusinc.com/about_1.html

Market position

vendor cites TSR market data ranking it #2 globally in BLE chip shipments in 2023; "hundreds of millions of IC products annually" and "over a hundred IoT clients" are vendor-stated figures, not independently verified [Likely] — https://iotbusinessnews.com/2023/09/29/78978-tsr-market-update-bluetooth-low-energy-market/; http://en.phyplusinc.com/about_1.html

Security note

No PhyPlus-specific CVE in NVD or CISA KEV as of 2026-06-15; CVE-2025-54646 (surfaced in search) is a Huawei EMUI/HarmonyOS BLE issue, NOT PhyPlus. General BLE risks (fingerprinting, proximity tracking, SoC-class bugs like BLEEDINGBIT affecting other vendors) apply to any BLE node but do not name PhyPlus; device security depends on OEM firmware. [Likely] — https://nvd.nist.gov/; https://www.cisa.gov/known-exploited-vulnerabilities-catalog; https://www.armis.com/research/bleedingbit/

Registration date

Unknown — IEEE publishes no registration dates; third-party "date registered" values are database artifacts and are not attributed here [Unknown]

Analyst note

A PhyPlus OUI identifies a BLE/IoT end node (smart home, wearable, hearable, sensor), not network infrastructure; expect it alongside Tuya-class consumer devices. The two registry names are one corporate group — match both. Don't display any third-party date as an IEEE registration date.