UTStarcom, Inc. — 4 prefixes (MA-L)

UTStarcom traces to the 1995 merger of Unitech Industries and Starcom Networks (each founded 1991), and went public on NASDAQ in March 2000 before restructuring into today's UTStarcom Holdings Corp, headquartered in Beijing. The IEEE MA-L registry carries four separate blocks under UTStarcom name variants: a bare "UTSTARCOM" registration at 00:E0:8E tied to an Iselin, NJ address, two "UTStarcom Inc" blocks (00:07:BA, 00:1B:DA) registered to the Alameda, CA headquarters used during the company's earlier US-telecom-equipment era, and a fourth block (48:EE:86) registered directly to "UTStarcom (China) Co.,Ltd" in Beijing, reflecting the later shift of manufacturing and corporate control to China. Historically the OUIs mapped to consumer/SMB-facing hardware — the F1000 VoIP Wi-Fi handset and the BAS 1000 broadband access server — both of which carry documented, publicly disclosed hardcoded-credential/backdoor vulnerabilities from the mid-2000s. The current UTStarcom product line has moved upmarket to carrier-grade packet optical transport, PON/broadband access, SDN, and 5G transport routers, so a UTStarcom OUI hit today is more likely to surface in a service-provider network than a home LAN.

IEEE assignments

4 MA-L blocks under UTStarcom name variants — 00:E0:8E ("UTSTARCOM", Iselin NJ US), 00:07:BA ("UTStarcom Inc", Alameda CA US), 00:1B:DA ("UTStarcom Inc", Alameda CA US), 48:EE:86 ("UTStarcom (China) Co.,Ltd", Beijing CN) [Confirmed] — the IEEE MA-L registry (cached IEEE MA-L registry)

Registry / block size

MA-L (24-bit OUI) for all 4 matches; no MA-M or MA-S entries found for any UTStarcom name variant [Confirmed] — the IEEE MA-L registry, the IEEE MA-M registry, the IEEE MA-S registry (zero non-MA-L matches)

Slug scope

bare slug vendor-utstarcom treated as the consolidating entry for all 4 blocks, consistent with the site's normaliseName() convention where legal-entity suffixes ("Inc", "(China) Co.,Ltd") strip to the bare name (per vendor-siemens-ag.md precedent)

[Likely] — inferred from repo convention, not an authoritative site-code citation

HQ / country

dispersed across 3 addresses — Alameda, CA, US (current/former US HQ, 2 blocks); Iselin, NJ, US (legacy address, 1 block); Beijing, CN (China subsidiary, 1 block) [Confirmed] — IEEE MA-L registry rows

Company status

active as UTStarcom Holdings Corp, HQ Beijing; original UTStarcom Inc. founded 1995 (Unitech Industries + Starcom Networks merger, both founded 1991), NASDAQ IPO March 2000 [Confirmed] — https://en.wikipedia.org/wiki/UTStarcom, https://utstar.com/about-us/company-overview

Device types

historically VoIP/Wi-Fi handsets (F1000 series) and broadband access server equipment (BAS 1000); current line is carrier-grade telecom infrastructure (packet optical, PON/broadband access, SDN, 5G transport routers) [Likely] — https://www.utstarcom.com/en/products, https://www.cvedetails.com/product-list/product_type-/vendor_id-1414/firstchar-/page-1/Utstarcom.html

Notable products

F1000 VoIP WiFi Phone, BAS 1000 broadband access server (legacy); current packet optical / PON access / SDN / 5G transport product lines [Confirmed] — https://www.utstarcom.com/en/products

Security context

two documented legacy hardcoded-credential/backdoor findings — F1000 VoIP WiFi Phone v2.0 (VxWorks) telnet daemon with default account target/password (CVE-2005-3717); BAS 1000 firmware 3.1.10 with multiple backdoor accounts (field/*field, guru/*3noguru, snmp/snmp, dbase/dbase). Both tied to specific discontinued mid-2000s product lines, not current UTStarcom Holdings Corp hardware [Confirmed] — https://www.northit.co.uk/cve/2005/3717, https://www.cvedetails.com/version/391590/Utstarcom-F1000-Voip-Wifi-Phone-2.0.html

allocated_date

Unknown — IEEE publishes no registration/allocation date for any of the 4 MA-L assignments; none recorded, none inferred, no epoch/placeholder used [Confirmed] — the IEEE MA-L registry (columns: Registry, Assignment, Organization Name, Organization Address only)

iana_reference

Blank/not applicable — OUI/MAC assignments are an IEEE registry matter, not IANA; no RFC reference exists and none was fabricated [Confirmed]

Related vendors

none identified beyond the UTStarcom (China) Co.,Ltd subsidiary already captured as a separate registry row [Unknown]

Analyst note

4 independently-sourced OUI rows across 3 org-name strings and 2 country addresses (US legacy sites + Beijing subsidiary) satisfy the multi-OUI/company-substance bar for a full entry rather than a shell abstention; a UTStarcom hit today skews carrier/service-provider rather than consumer LAN given the company's current product focus [Confirmed]