Hypervolt Ltd holds a single MA-L (24-bit, large-block) OUI assignment with prefix 6C:0F:61, registered to "Hypervolt Ltd" at 25 Churchill Place, London E14 5EY, GB. Hypervolt manufactures Wi-Fi- and Bluetooth-connected residential EV (electric vehicle) charging wallboxes — EVSE units — so a 6C:0F:61 address seen on a home or small-business LAN almost certainly belongs to an EV charger appliance, not a general-purpose computer, phone, or router. The chargers join the home Wi-Fi network, are commissioned and managed through a companion smartphone app, and phone home over outbound HTTPS to Hypervolt's cloud backend for scheduling, over-the-air firmware updates, and smart-home/solar-tariff integrations (e.g. Amazon Alexa). Bluetooth is used for initial setup/commissioning only. On the security side, Pen Test Partners audited several EV charger brands including Hypervolt in 2021 and noted that early units used a Raspberry Pi compute module lacking a secure bootloader — meaning stored data such as Wi-Fi credentials could in theory be extracted with physical access — but no remote-code-execution or network-exploitable flaw was confirmed for Hypervolt specifically, and the risk was assessed as low given the physical-access prerequisite. Hypervolt states its current Home 3 Pro meets UK EV charger cybersecurity regulations and includes anti-tamper detection. No public CVEs specific to Hypervolt were found as of June 2026. As with all IEEE OUI data, no assignment/registration date is published — any "date registered" on third-party MAC lookup sites is a database artifact, not an IEEE fact.
- IEEE assignment
- 6C:0F:61 → Hypervolt Ltd [Confirmed] — enrichment/registries/oui.csv line 657; https://hwaddress.com/company/hypervolt-ltd/
- Registry / block size
- MA-L (24-bit OUI); range 6C:0F:61:00:00:00 – 6C:0F:61:FF:FF:FF (~16.7M addresses); sole registered block (not present in MA-M/oui36) [Confirmed] — enrichment/registries/oui.csv (mam.csv/oui36.csv negative), https://hwaddress.com/company/hypervolt-ltd/
- HQ / country
- 25 Churchill Place, London E14 5EY, GB [Confirmed] — enrichment/registries/oui.csv, https://hwaddress.com/company/hypervolt-ltd/
- Company status
- active [Confirmed] — https://hypervolt.co.uk/
- Device types
- residential EV charging wallboxes (EVSE) — e.g. Hypervolt Home 3 / Home 3 Pro [Confirmed] — https://hypervolt.co.uk/, https://whatwallcharger.com/chargers/hypervolt-home-3-0/, https://www.smarthomecharge.co.uk/chargers/hypervolt/home-3-pro/
- Connectivity
- Wi-Fi (2.4/5 GHz, vendor describes a 256-bit encryption / cryptography engine for WLAN) for cloud control + OTA; Bluetooth for initial commissioning only [Confirmed] — https://whatwallcharger.com/chargers/hypervolt-home-3-0/, https://www.smarthomecharge.co.uk/chargers/hypervolt/home-3-pro/
- Assignment date
- not published by IEEE [Unknown] — IEEE OUI data carries no registration date; third-party "date registered" fields are database artifacts
- Security context
- Pen Test Partners (2021) flagged early Hypervolt units using a Raspberry Pi compute module without a secure bootloader (physical-access data-extraction risk, e.g. Wi-Fi creds); no confirmed remote/network-exploitable flaw, risk assessed low; current Home 3 Pro stated to meet UK EV-charger cyber regs with anti-tamper detection; no Hypervolt-specific public CVEs as of June 2026 [Confirmed] — https://www.pentestpartners.com/security-blog/smart-car-chargers-plug-n-play-for-hackers/, https://whatwallcharger.com/chargers/hypervolt-home-3-0/
- Network exposure
- outbound HTTPS to Hypervolt cloud for scheduling/OTA/app sync; no inbound listening ports or UPnP exposures publicly documented; consumer IoT appliance in the smart-home/energy category [Likely] — https://support.hypervolt.co.uk/en/knowledge-base/getting-started, https://support.ev.energy/en/support/solutions/articles/80001164106-hypervolt-home-pro-3-is-showing-as-offline
- Analyst note
- a 6C:0F:61 device on a LAN is almost certainly a Hypervolt home EV charger — classify it as smart-home/energy IoT, expect cloud-bound HTTPS, and isolate IoT appliances on a segmented VLAN as a general best practice.