AMPAK Technology, Inc. — 42 prefixes (MA-L)

AMPAK Technology, Inc. is a Taiwan-based wireless-module ODM that holds 42 MA-L (24-bit OUI) blocks registered to "AMPAK Technology, Inc." — an unusually large footprint that reflects its role as a high-volume component supplier rather than an end-product brand. AMPAK does not ship consumer devices under its own name; it builds Wi-Fi and Bluetooth combo modules (the AP6xxx series) that downstream OEMs embed into single-board computers, media-streaming boxes, tablets, IP cameras, smart-home appliances, POS terminals, and industrial and automotive equipment. The modules are built around Broadcom — now Synaptics — silicon (e.g. BCM43362, BCM43430, BCM43455, BCM4330) over SDIO interfaces, driven by the Linux brcmfmac/bcmdhd stack, which is why AMPAK prefixes turn up on Banana Pi, Orange Pi, Khadas, and similar embedded Linux boards. The practical consequence for network operators: an AMPAK OUI identifies the wireless module, not the host device. The actual appliance — its model, firmware, and security posture — belongs to whatever OEM integrated the module, and those devices frequently expose no user-visible hostname, so OUI lookup is often the only identification handle available. An AMPAK MAC on a scan is therefore expected and benign in itself; the right follow-up is to identify the host product, not to treat the AMPAK prefix as suspicious. The registry records several Taiwan address variants across the 42 blocks (Hukou and Zhubei in Hsinchu, plus an earlier Taoyuan address on the 00:22:F4 block), consistent with facility moves over the company's history.

IEEE assignment

42 prefixes → AMPAK Technology, Inc., registered Taiwan (R.O.C.) [Confirmed] — IEEE MA-L; count corroborated by Netify

Registry / block size

MA-L (24-bit OUI); 42 IEEE prefixes. No MA-M or MA-S allocations exist (the IEEE MA-M registry and the IEEE MA-S registry return no AMPAK hits) [Confirmed] — IEEE MA-L/MA-M/MA-S registries. NOTE: IEEE's public OUI data publishes NO assignment/registration date (the IEEE MA-L registry columns are only Registry, Assignment, Organization Name, Organization Address); maclookup.app's "25 October 2008" for AMPAK is a third-party database artifact, not an IEEE fact.

HQ / country

Zhubei City, Hsinchu County, Taiwan (6F., No. 23, Huanke 1st Rd., Zhubei City, Hsinchu County 302047); registry also records legacy Hukou (Hsinchu Industrial Park) and Taoyuan (Jhongli) addresses across older blocks [Confirmed] — IEEE MA-L, ampak.com.tw

Company status

active [Confirmed] — ampak.com.tw

Device types

Wi-Fi/Bluetooth combo modules (component supplier); host devices include single-board computers, media-streaming boxes, tablets, IP cameras, smart speakers, POS systems, industrial and automotive equipment [Confirmed] — ampak.com.tw, deviwiki.com, stellastra.com

Notable products

AP6xxx-series Wi-Fi/BT modules (AP6181, AP6210, AP6212A, AP6234A, AP6256, AP6335, AP6356S, AP6398XU); form factors Stamp/LGA/M.2/Industrial; also SOM, 5G, and GNSS modules [Confirmed] — ampak.com.tw, deviwiki.com

Chipset partnership

modules use Broadcom/Synaptics Wi-Fi+BT silicon (BCM43362, BCM43430, BCM43455, BCM4330; BT BCM20710/BCM40183), SDIO interface, Linux brcmfmac/bcmdhd drivers [Confirmed] — deviwiki.com, ampak.com.tw

Verified sample prefixes (all MA-L, AMPAK Technology, Inc.)

00:22:F4, 10:D0:7A, 6C:FA:A7, AC:83:F3, B0:F5:C8, 54:96:CB [Confirmed] — IEEE MA-L

Security note

no AMPAK-specific CVEs or public vulnerability disclosures found in NVD/CISA as of 2026-06-20. An AMPAK MAC indicates a downstream OEM device containing an AMPAK module; security posture depends on the host device's firmware, not the module vendor [Confirmed] — NVD/CISA (no hits), stellastra.com

Related vendors

integrates Broadcom/Synaptics chipsets; widely paired with embedded-Linux SBC vendors (Banana Pi, Orange Pi, Khadas)

Analyst note

an AMPAK OUI reliably identifies the wireless module but not the host appliance; embedding devices often lack visible hostnames, so OUI lookup is the primary identification method. The prefix is expected/benign on its own — identify the host product rather than treating it as suspicious.