AO (АО «НПК РоТеК» — NPK RoTeK) — 4 prefixes (MA-L)

The IEEE OUI registry lists this vendor under the bare name "AO" — not a company name but the Russian legal-form prefix Акционерное общество (joint-stock company), the rough equivalent of "JSC." Behind that abbreviation sits AO NPK RoTeK (АО «НПК РоТеК»), a Moscow-based manufacturer of telecom subscriber equipment and industrial IoT hardware. Four MA-L blocks (48:29:E4, DC:E3:05, D8:AF:81, 1C:CA:41) are registered to "AO" at three Moscow addresses, two of them sharing the Prospekt Mira location (postcode 129223). The identification rests on cross-matching those registry addresses against several third-party MAC databases, which resolve them to NPK RoTeK; a fifth, earlier block (EC:4C:4D) carries the company's former legal name "ZAO NPK RoTeK," reflecting the 2014 Russian Civil Code reform that abolished the ZAO (closed joint-stock) form and pushed later registrations to the "AO" prefix. RoTeK's product line targets Russian telecom operators and utilities under the country's import-substitution program: GPON ONTs and broadband CPE (the RX-33412 ships on Rostelecom networks), VoIP gateways, Ethernet switches, LoRaWAN IoT devices, and smart energy meters. No RoTeK-specific CVEs or botnet incidents surfaced; the generic GPON CPE device class carries known RCE and botnet-targeting history (e.g. CVE-2018-10562, Mirai-family activity), but nothing ties those to RoTeK hardware specifically, and deployment appears confined to Russia.

IEEE assignment

4 MA-L prefixes → org name "AO", registered Moscow, RU [Confirmed] — IEEE MA-L (lines 1065, 9937, 17400, 24021)

Registry / block size

MA-L (24-bit OUI); 4 prefixes under bare name "AO" [Confirmed] — IEEE MA-L. NOTE: IEEE's public OUI data publishes NO assignment/registration date; any "date registered" on third-party tools is a database artifact, not an IEEE fact.

Verified prefixes (all MA-L, "AO")

48:29:E4 (Prospekt Mira, Moscow 129223), DC:E3:05 (Prospekt Mira, Moscow 129223), D8:AF:81 (Filippovskiy per. 8/1, Moscow 119019), 1C:CA:41 (Verhnyaya Krasnoselskaya 11A bldg 3, Moscow 107140) [Confirmed] — IEEE MA-L

Country / city

Russia (RU), Moscow [Confirmed] — IEEE MA-L

Company identification

org name "AO" resolves to АО «НПК РоТеК» (AO NPK RoTeK) via registry-address cross-match against third-party MAC databases [Likely] — devtools360.com (DCE305), cleancss.com (DC-E3-05), hwaddress.com (zao-npk-rotek), udger.com. "AO" alone is the joint-stock-company suffix, not a complete name.

Name history

earlier block EC:4C:4D registered as full former legal name "ZAO NPK RoTeK"; ZAO→AO reflects the 2014 Russian Civil Code reform abolishing the ZAO (closed joint-stock) form [Likely] — udger.com (zao_npk_rotek), hwaddress.com; reform context is general Russian corporate-law fact

Device types

GPON ONT/routers (RX-33412 on Rostelecom), broadband CPE (ADSL/VDSL/FTTB/DOCSIS), VoIP gateways, Ethernet switches, LoRaWAN/IoT devices, smart energy meters (RTM series), industrial controllers, power/UPS systems [Likely] — npkrotek.ru, rotek.ru/solutions/telekom, admin-router.ru (rotek-rx-33412)

Company status

active; Moscow-based manufacturer/system integrator; certified domestic ("import substitution") producer under MINPROMTORG registry [Likely] — npkrotek.ru, tadviser.com (NPK_ROTEK), zoominfo.com

Website

https://npkrotek.ru/ (related brand NTC Rotek at https://www.rotek.ru/) [Likely] — npkrotek.ru

Allocated date

Unknown — IEEE publishes no OUI registration dates; third-party artifact dates (maclookup.app: D8:AF:81 "8 Apr 2019", 1C:CA:41 "12 Nov 2022") are database metadata, not IEEE facts, recorded for reference only [Unknown]

Security context

no RoTeK-specific CVEs, CISA advisories, or botnet incidents found; generic GPON CPE class has known RCE (CVE-2018-10562) and botnet (Mirai/Hajime/Satori) history not tied to RoTeK; deployment appears Russia-confined [Likely] — radware.com (gpon-routers-botnet), bleepingcomputer.com (gpon-routers)

Analyst note

the bare "AO" registry name is ambiguous and easy to mis-list; company identity is inferred from address cross-matching, so tag it Likely rather than Confirmed. An "AO" OUI on a globally-administered address indicates RoTeK hardware, but the abbreviation alone is not self-identifying.