Car Hacking Village
The DEF CON 32 Car Hacking Village edition whose official badge sale page, public CHV repositories, CTF archive, SAO specification, and IOActive key-fob badge build series document a CAN-bus badge ecosystem.
Las Vegas Convention Center, Las Vegas, Nevada / DEF CON 32 · United States · 2024
Car Hacking Village's DEF CON 32 badge ecosystem centered on a main RP2040 badge with CAN-network surfaces, four CHV SAO connectors, public board and firmware repositories, public CTF challenge notes, and IOActive's separately documented key-fob badge / SAO build.
Lifecycle
IOActive's build series documents a key-fob badge / SAO for DEF CON 32 CHV with dsPIC33CK32MP502, CAN transceiver, NeoPixels, touch buttons, IR, 125 kHz RFID receive, and 433 MHz transmit surfaces.
The public CTF archive ties the Speedometer SAO to rock-paper-scissors behavior, CAN messages, firmware reversing, and LCD output used in the challenge.
The public Speedometer SAO firmware repository is MIT-licensed and says it includes CTF problem and notes material built on a display library.
The CHV SAO spec provides 3.3 V and ground while replacing normal SAO I2C with CAN TX and CAN RX for vehicle-network add-ons.
The public challenge archive documents main-badge CAN enumeration, a physical-inspection flag under the battery pack, random traffic, and a UART Python REPL path.
The firmware repository describes firmware intended to emulate a car on one PCB, with C and Python areas, verification files, RP2040 flashing workflow, and socketcan/cansniffer output.
The official CHV page documents the 2024 main badge with an RP2040, four CAN networks, a dry CAN connector, and four SAO connectors, while the public board tree preserves KiCad and production files.
Operational history
The record remains image-free rather than copying event-page images, blog photos, repository images, social previews, screenshots, generated art, or approximate badge artwork.
The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.
The catalogue cites those repositories as source evidence but does not treat repository images, board renders, firmware, CTF material, or documentation as broadly reusable publication assets without explicit license coverage.
The compendium keeps the badge under its own village lineage while preserving DEF CON event context and avoiding an attendee-wide DEF CON main-badge claim.