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

AMPAK Technology, Inc., founded in 2000 (Hsinchu, Taiwan), 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 addresses trace a relocation history: early blocks list 3F, No.15-1 Zhonghua Road, Hsinchu Industrial Park, Hukou; a mid-period cluster lists No.1 Jen Ai Road in the same park; the three most recent blocks (54-96-CB, 24-36-72, B0-F5-C8) list 6F., No.23, Huanke 1st Rd., Zhubei City, Hsinchu County; and one outlier (00-22-F4) lists a Jhongli/Taoyuan address — consistent with facility moves over the company's history. One cross-vendor caveat: because the PCIe variants are often driven directly, the same modules frequently surface under Broadcom OUIs (14:E4 family) instead of an AMPAK-registered prefix, so absence of an AMPAK OUI does not rule the module out.

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 addresses vary by block: early — 3F, No.15-1 Zhonghua Road, Hsinchu Industrial Park, Hukou, Hsinchu 30352; mid-period — No.1, Jen Ai Road, Hsinchu Industrial Park, Hukou, Hsinchu 30352; newest (54-96-CB, 24-36-72, B0-F5-C8) — 6F., No.23, Huanke 1st Rd., Zhubei City, Hsinchu County 302047; one outlier (00-22-F4) — No. 8-1, Nanyuan 2nd Rd., Jhongli, Taoyuan 320

[Confirmed] — IEEE MA-L, ampak.com.tw

Company status

active [Confirmed] — ampak.com.tw

Founding year

2000 (company fact, not a MAC/OUI date) [Confirmed] — ampak.com.tw/about/about-ampak

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 combo modules (AP6181, AP6201, AP6210, AP6212/A, AP6232F, AP6234A, AP6255, AP6256, AP6330, AP6335, AP6356, AP6356S, AP6359SA, AP6398XU, AP6441, AP6452, AP6474); form factors Stamp/LGA/M.2/SDIO/Industrial; also SOM, 5G, and GNSS modules, plus the WSDB-720GN and WUBB-743GN USB Wi-Fi dongles (some older USB modules used Ralink silicon rather than Broadcom)

[Confirmed] — ampak.com.tw, deviwiki.com/wiki/AMPAK

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 (8 of the 42 MA-L blocks, all AMPAK Technology, Inc.)

00:22:F4, 10:D0:7A, 6C:FA:A7, AC:83:F3, B0:F5:C8, 54:96:CB, 00:2D:B3, 24:36:72 [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

Cross-vendor caveat

because the PCIe variants of these modules are often driven directly, AMPAK modules frequently surface under Broadcom OUIs (14:E4 family) rather than an AMPAK-registered prefix [Likely — community/wiki sourced] — deviwiki.com/wiki/AMPAK

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.