Hacker Con Badges

Not just specs

Issues & Camp Impact

Safety warnings, delivery problems, app-store gaps, team-process history, and first-hand reports are tracked as sourced records.

Reset
2204 matching issue record(s)
BSides NOLA 2026 Rougarou Circuit Board Badge note

hardware and software specification gap · primary and first-hand source trail · needs badge-team documentation

Public sources establish a custom PCB/circuit-board badge but do not identify any electronic components, active behavior, power source, board dimensions, schematic, BOM, Gerbers, firmware, programming method, or challenge implementation.

The record preserves the verified physical PCB form while withholding an electronic-device, firmware, component, or challenge claim until Fox Pick, BSidesNOLA, or another primary archive provides it.

Source note: BSides Global event listing, NOLABSides site, BSidesNOLA organizer updates, and Liz Gore attendee account.

HackNWA 2026 VIP Assembled Badge note

hardware and software specification gap · ticket wording and event activity context only · no artifact-level technical release recovered

The phrase VIP Assembled Badge and the event's hardware-hacking activity do not identify an electronic badge, PCB, kit, material, artwork, QR/RFID/NFC function, controller, battery, display, connector, schematic, BOM, firmware, app, challenge linkage, binary, source release, licence, flashing path, or physical credential behavior.

The record remains an explicitly ticket-listed identity artifact rather than inventing electronics, software, CTF integration, or a finished construction from a tier name.

Source note: HackNWA official event page, organizer announcement, registration page, and contemporaneous ticket listing.

Area41 2018 Proteus Badge note

hardware archive gap · source-conservative public archive · needs schematic or BOM recovery

The source set proves ESP8266, WiFi, display, button inputs, and firmware behavior, but not a complete schematic, BOM, PCB revision, display part number, enclosure, or battery specification.

The hardware section intentionally avoids component-level claims beyond public sources until an original hardware archive or transcript is recovered.

Source note: Compass Security wrap-up, Proteus README, and platformio.ini.

BSides Kristiansand 2025 Sykt Badge note

hardware archive gap · post-event report and attendee observation · needs badge-team archive

The recovered public trail proves the electronic duck badge, CTF LEDs, and observed RP2040/MicroPython behavior, but does not expose schematics, PCB files, BOM, official firmware source, case files, or production files.

The catalogue records observed hardware and software behavior while avoiding unrecovered component, board-source, and manufacturing claims.

Source note: Noroff post-event report, BSides Kristiansand recordings page, and Cryptax technical write-up.

Hack&Roll 2026 Quack & Roll Badge note

hardware archive gap · current public archive · needs deeper recovery

The recovered public repository documents firmware and components but does not expose schematics, PCB layout files, BOM, Gerbers, or full manufacturing files for the badge.

Hardware claims stay limited to the organizer posts, repository README, code, component registry, and acknowledgements.

Source note: nushackers/hnr26-badge-workshop repository and Espressif Component Registry entry.

ROOTCON 11 Electronic Badge note

hardware archive gap · source-backed but incomplete · needs technical archive recovery

The recovered public sources prove an official ROOTCON 11 electronic badge but do not document its components, firmware, schematic, board files, artwork source, production run, or attendee distribution details.

The dossier keeps the electronic-badge claim tied to official sponsor-kit wording and avoids unsupported hardware or software details.

Source note: ROOTCON 11 archive and partnership kit.

ROOTCON 12 Electronic Badge note

hardware archive gap · source-backed but incomplete · needs technical archive recovery

The recovered public sources prove ROOTCON 12 event context, official badge inclusion, and a maker-post electronic-badge title, but do not document components, firmware, schematic, board files, artwork source, production run, or attendee distribution details.

The dossier keeps the electronic-badge classification conservative and avoids unsupported hardware or software details until a technical archive or first-hand design writeup is recovered.

Source note: ROOTCON 12 archive, ROOTCON 12 quick guide, and Jay Turla / @shipcod3 maker post.

ROOTCON 13 Programmable Badge note

hardware archive gap · source-backed but incomplete · needs technical archive recovery

The recovered public sources prove a ROOTCON 13 custom programmable conference badge and badge logo-placement add-on, but do not document components, firmware, schematic, board files, artwork source, production run, or shipped badge variants.

The dossier keeps the programmable-badge claim tied to the official sponsor prospectus and avoids unsupported hardware or software details.

Source note: ROOTCON 13 archive, quick guide, media directory, and sponsors prospectus.

HITBSecConf2019 Amsterdam Badge note

hardware archive gap · official source but incomplete · needs deeper archive recovery

The official archive confirms a special-edition electronic badge and Badge Village hacking path, but this pass did not recover component list, schematic, BOM, board files, exact chip, production count, or firmware repository.

The dossier records the verified anniversary-badge context while avoiding unsupported component-level claims.

Source note: HITBSecConf2019 Amsterdam archive.

HITB+CyberWeek 2021 Packet Hack Badge note

hardware archive gap · source-backed but incomplete · needs schematic or BOM recovery

The recovered sources document the wearable badge, OLED, controls, headers, pinouts, AVR/ISP flashing, firmware behavior, and CTF mode, but this pass did not recover a schematic, BOM, board files, exact MCU package, or production quantity.

The record stays at source-backed hardware surfaces and avoids unsupported component-level claims.

Source note: Hackster Packet Hack Badge project and GitHub firmware repository.

Ruxcon 2016 HHV Badge note

hardware archive gap · source-backed but incomplete · needs schematic or PCB archive

The recovered source trail proves the RuxBadge BOM, assembly workflow, STM32F030, IR components, LED array, boot jumper, CR2032 power, firmware, and IR protocol, but this pass did not recover schematic, PCB files, Gerbers, manufacturing count, or a project license.

The record keeps hardware claims to the build PDF and repository README instead of inventing board-layout, distribution-volume, or licensing detail.

Source note: RuxBadge instruction sheet, Darkglade source-release post, and ruxconhhv2016 repository.

Ruxcon 2017 HHV Badge note

hardware archive gap · source-backed but incomplete · needs schematic or PCB archive

The recovered source trail proves an assembled Ruxcon 2017 HHV badge, UART adapter requirement, ESP8266/NodeMCU firmware, and challenge behavior, but this pass did not recover schematic, PCB files, BOM, manufacturing count, or exact board revision.

The record keeps component claims to ESP8266/NodeMCU evidence and avoids unsupported board-layout or production-run detail.

Source note: Ruxcon 2017 HHV page, Darkglade writeups, source-release post, and ruxconhhv2017 repository.

BSides Canberra 2016 Arduino Running-Order Badge note

hardware archive gap · source-backed but incomplete · needs primary badge archive

The recovered sources document a home-made Arduino badge and running-order display, but not a schematic, BOM, firmware, exact Arduino board, display part, artwork, or production archive.

The catalogue records the verified electronic-badge behavior while avoiding unsupported claims about circuit design, parts, firmware, or challenge features.

Source note: BSides Canberra 2016 event page and The Register event report.

LCA2019 E-ALE Floral Bonnet note

hardware archive gap · source-backed but incomplete · needs board repository recovery

The recovered source trail documents the board role, Raspberry Pi Zero WH target, major peripherals, lab use, and kit price, but this pass did not recover schematic, PCB, BOM, firmware, or exact sensor-part correction beyond the page text.

The entry keeps claims to the official component list and training context while avoiding unsupported board-revision, driver-source, or manufacturing-quantity details.

Source note: LCA2019 E-ALE page, E-ALE Linux.conf.au 2019 page, and Floral Bonnet walkthrough.

LCA2021 SwagBadge note

hardware archive gap · source-backed but incomplete · needs stable public hardware archive

Official LCA2021 pages document SwagBadge/DagBadge hardware, firmware, SAOs, MicroPython/Aiko software, and tested shipped badges, but this pass did not recover a stable schematic, BOM, Gerber, PCB, firmware-source, or license archive.

The entry describes the public conference-badge programme and keeps component-level claims limited to sourced high-level evidence.

Source note: LCA2021 Open Hardware Miniconf, SwagBadge talks, and Adafruit Daily secondary note.

LCA2022 SwagBadge and Rockling SAO Kit note

hardware archive gap · source-backed but incomplete · needs stable public hardware archive

Official LCA2022 pages document hardware kits, an updated SwagBadge, FPGA SAOs, Rockling and SAO sessions, and a hardware-design talk, but this pass did not recover a stable schematic, BOM, bitstream, firmware, PCB, or repository license archive.

The entry captures the event-backed kit and badge lineage while avoiding unsupported chip-part, board-revision, firmware, or shipped-behavior claims.

Source note: LCA2022 ticketing news, Open Hardware Miniconf page, and schedule/talk pages.

Off-By-One 2024 Hardware Badge note

hardware archive gap · source-backed but incomplete · needs public badge-team archive

The public source trail documents components, visible board behavior, and challenge surfaces, but this pass did not recover a public schematic, KiCad tree, BOM, firmware repository, Gerbers, production quantity, or official badge-team release.

Hardware and software fields stay limited to the attendee writeup, licensed photos, and public event context.

Source note: elmo writeup, AiSP event listing, and current Off-By-One site.

DEF CON Singapore 2026 HFSDR Badge note

hardware archive scope · source-backed but incomplete · needs post-event production reconciliation

The public archive preserves firmware, host software, and a hardware directory, but this pass does not reconcile final manufactured units, BOM revisions, production lot, or full shipped feature parity with the preorder list.

Hardware claims are limited to preorder text, repository structure, README behavior, and host-guide protocol documentation.

Source note: r/Defcon preorder post, rhgndf/hfsdr README, host guide, and CH32V305 firmware README.

Pwnterrey 2026 Official ESP32-C5 Badge note

hardware build, power, RF, and safety documentation gap · public KiCad repository and README · design-level evidence only

The public KiCad project identifies controller, NFC, USB-C, and GPS design material, but the reviewed sources do not supply a complete BOM, fitted-part list, PCBA record, battery or charging design, power budget, antenna/final RF implementation, measurements, certification, thermal or fault behavior, safe-modification guidance, or a verified finished configuration.

Published design references are not treated as a build recipe, electrical-safety endorsement, radio-performance claim, certification claim, or proof that every public component was fitted to every event unit.

Source note: ElectronicCats/badge-pwnterrey-2026 repository and hardware tree.

OzSec 2025 CRASHANDBURN Badge note

hardware configuration and BOM gap · primary work-in-progress repository · final configuration unconfirmed

The public BOM identifies alternative displays, an RP2350 section, an ESP32-S3 option, and an ESP32-specific pinout, while its own header calls the BOM work in progress. It does not establish the controller, display, PCB revision, battery, enclosure, component population, or electrical behavior of a final artifact.

The record can show the documented development directions without collapsing alternatives into an invented production specification.

Source note: OzSecICT badge-crashandburn component BOM and ESP32 pinout.

Women's International Cybersecurity Challenge 2026 CTF Badge note

hardware configuration and delivery scope gap · primary maker documentation · configuration and allocation not publicly mapped

The maker documentation targets ESP8266 / ESP32 hardware and shows a cased device, but does not map a final board, parts population, power system, radio configuration, firmware build, production run, recipient list, handoff, or attendance eligibility to WICC units.

The catalogue records the documented electronic CTF platform without inventing a universal configuration, quantity, delivery outcome, or attendee credential role.

Source note: Commit-pinned OzmoOzmo SecurityConferenceCTFBadge README and repository contents.

Div0 Tingkat eBadge (DEF CON Singapore 2026) note

hardware configuration, power, and distribution scope gap · commit-pinned firmware, support notes, and repository tree · Pico-class source surface published; physical-unit configuration unrecovered

The source publishes Pico SDK code, an RP2040-focused support helper, pin declarations, a UF2, and SAO EDA files. It does not publish a main-badge schematic, PCB layout, BOM, exact controller/package, display part, LED population, battery or power path, charging/protection design, pinout/SAO compatibility, assembly/testing evidence, production count, serial/revision inventory, recipient list, price, pickup, mailing terms, or completed delivery. The EDA material is under SAO/adapter paths and is not promoted into an undocumented main-badge hardware release.

Readers can inspect the source-backed electronic surface without treating it as an electrical guarantee, a safe host/SAO compatibility statement, a full open-hardware release, or proof of how many real badges were made or received.

Source note: Commit-pinned firmware source, RP2040 support notes, and repository tree.

DOJOConf Panamá 2026 Electronic Badge note

hardware deployment, firmware, and license-scope boundary · commit-pinned public source and event offer · public design source found; event-unit deployment scope remains open

The self-described official archive now documents a CH573F RISC-V/BLE design, OLED, buttons, WS2812B LED, USB-C, battery connection, KiCad files, and root CERN Open Hardware Licence v1.2 text. It does not identify the source commit, binary, battery type, charging implementation, component substitutions, assembly state, or support status of each event unit. The hardware-design license does not automatically cover firmware, repository media, event media, logos, or trademarks.

The entry can preserve the public technical surface without presenting it as a verified per-recipient build, final factory image, safety certification, or broad media-reuse grant.

Source note: ElectronicCats/badge-dojocon-2026 commit 5f54b75f6e7011b59d98899939a9954ad415cca4 README, hardware tree, LICENSE, and v1.0 release; DOJOConf Panamá official event page.

ICS Village DEF CON 34 Badge note

hardware design and safety documentation gap · official specification page · needs engineering archive

The official page gives an unusually detailed feature list but does not provide a schematic, BOM, PCB/Gerbers, transceiver or PHY part identities, isolation details, bus-voltage limits, termination values, charging circuit, battery chemistry, dimensions, complete connector wiring, or electrical safety guidance.

The record can name the published interfaces without suggesting that the badge is reproducible, electrically characterized, isolated, or safe for any specific live system.

Source note: FREE-WILi ICS Village DEF CON 34 Badge page.

DEF CON Singapore 2026 Public Safety Village Badge note

hardware detail caveat · official article but narrow technical detail · needs public technical archive

HTX's launch article proves a Public Safety Village badge artifact and visible illuminated emergency-vehicle icons, but no reviewed public source publishes a MCU, schematic, firmware, BOM, battery, distribution count, or challenge protocol for this badge.

The record documents the verified village badge artifact without inventing electronics, firmware, production, or distribution details.

Source note: HTX launch article, HTX Public Safety Village page, and HTX preview article.

RomHack Camp 2026 Badge note

hardware licence gap · repository LICENSE · firmware licensed; hardware and artwork unlicensed

The repository LICENSE covers only the Tactility and Retro-Go firmware trees and the bundled Doom shareware notice; the schematic, Gerbers, BOM, branding assets, and setup-site illustrations carry no stated licence.

Hardware files are linked rather than mirrored, and no badge render or photo is reused.

Source note: CyberSaiyanIT/rhc2026-badge LICENSE, checked 2026-10-01.

X-CTF 2016 Badge note

hardware license caveat · GitHub API and repository tree recheck · no visible hardware license

The public hardware repository preserves Eagle design files and badge imagery but GitHub reported no detected license, and no top-level reusable hardware or image license was recovered in this pass.

Hardware files are cited as evidence, but repository images are not copied locally and reuse claims stay limited.

Source note: jellyjellyrobot/neander GitHub API and repository tree recheck.

Robotic Hacking Community DEF CON 34 AI-Connected Badge note

hardware production and power documentation gap · official documentation and MIT repository · firmware and interface documentation released; production record incomplete

The release identifies the MCU and several interfaces, but does not publish a schematic, BOM, Gerbers, PCB dimensions, battery or power chain, charging behavior, manufacturing run, final physical variants, electrical test results, safety documentation, or certification record.

Published firmware detail is not represented as a complete open-hardware, production, or safety dossier.

Source note: RHC official badge documentation and `rhc-badge-firmware` repository.

Portal Badge (DEF CON 34) note

hardware revision, bill-of-material, power, and safety boundary · public source tree · multiple source artifacts; final physical unit undocumented

The hardware project contains board variants, production/gerber paths, position data, acrylic files, and a source-defined MCU/LED/input/audio/SD surface, but not a reviewed final BOM or complete assembler/operator guide. It does not establish actual LED/input selection, battery or power configuration, current/thermal data, charge behavior, enclosure safety, radio behavior, dimensions, electrical test results, certification, or final revision shipped to participants.

The record does not transform source tree names and schematic/fabrication material into a verified production bill of materials, safety endorsement, repair guide, or field-operating recommendation.

Source note: Portal Badge hardware and firmware GitLab projects.

Celestial Wayfinder Badge (DEF CON 34) note

hardware revision, final bill-of-material, and interface boundary · maker listing and MIT firmware repository · multiple revisions documented

The product names an ESP32-S3/128×128/61-LED surface and five mechanical switches, while firmware documentation covers v1/v2/v3 boards and describes v3 plus four face buttons and an encoder. The sources do not map the offered DEF CON unit to a definitive revision, final board files, exact sensor/module selection, full BOM, pinout, dimensions, antenna, or manufacturing configuration.

The record retains supported feature families while avoiding a claim that the live offering exactly matches one repository branch, older board revision, or a complete production BOM.

Source note: Celestial Wayfinder Badge listing and `Celestial-Wayfinder` README.

DFIU SAO (DEF CON 34) note

hardware revision, power, connector, and safety documentation gap · public hardware tree and firmware pin declarations · source files published; final electrical and mechanical specification incomplete

The public hardware repository shows KiCad, BOM/position, and Gerber material, and the firmware declares CH32V003, touch, PWM audio, and LED paths. Reviewed sources do not establish final board revision/population, component substitutions, LED/speaker models, touch-electrode construction, SAO connector/version/pinout, input supply range, battery/charging path, current draw, voltage limits, protection, dimensions, enclosure, assembly process, test coverage, user instructions, safety warnings, EMC/RF/compliance evidence, or handling guidance.

The entry can point to a concrete design archive without presenting the SAO as electrically complete, interoperable with every host, safe for every power source, fabricated, tested, or compliance-validated.

Source note: dfiu-ch32v003-pcb repository, DFIU PlatformIO configuration, and DFIU main.c.

Rabbit-Labs The Pirates' Plunder Badge note

hardware source gap · source-backed but incomplete · needs public hardware archive

The recovered public sources document product context, pinouts, firmware behavior, and operating notes, but this pass did not recover schematics, Gerbers, KiCad files, BOM, manufacturing files, shipped quantity, or final assembly documentation.

Hardware claims stay limited to the product page, pinout text, and firmware constants without inventing board layout, production quantity, or undocumented circuit details.

Source note: Rabbit-Labs product page, badge pins.txt, and globals.h.

Avnet FAE Institute 2026 PCB Badge note

hardware source, production, and component-parity boundary · commit-pinned KiCad and Gerber source review · design and manufacturing files public; final unit unverified

The source archive publishes a KiCad board, custom footprints, and Gerbers, but the reviewed tree does not provide a final schematic, bill of materials, assembly instructions, manufacturer, order record, panel/assembly data, inspection log, final revision manifest, production count, component substitutions, or unit-by-unit build trace. The source snapshot predates the July event.

The record can describe the documented board design while avoiding a claim that the public files are the exact final build, that every event badge carried the listed footprints, or that the design was manufactured and tested at scale.

Source note: Commit d6865583b38e9631585fa126f37a46d859c91cf5 and the FAEI26_Clean KiCad/Gerber tree.

BSides SP 2026 Garoa Badge REV. 0 note

hardware source-reuse boundary · public repository metadata and reviewed root tree · needs explicit project license or permission

The Garoa wiki calls the project open hardware and its page content carries a CC BY-SA notice, but the reviewed BadgeGaroa_r2 root has no detected top-level repository license. Those facts do not establish reusable rights for all code, CAD, documentation, or images in the project tree.

The catalogue links to the technical source as evidence while withholding local copies of repository imagery, CAD, and source material until a clear reuse basis is identified.

Source note: Garoa Badge REV. 0 documentation, BadgeGaroa_r2 repository metadata/tree, and badge.gallery image policy.

BSides Knoxville 2025 Fox Pick ESP32-S3 Badge note

hardware specification boundary · maker-documented summary only · component-level overview public; engineering archive absent

The public talk names the ESP32-S3, display family, interaction and power features, but does not publish a board revision, PCB dimensions or artwork, schematic, Gerbers, BOM, exact display configuration, battery chemistry or capacity, component substitutions, radio certification, test results, or final production configuration.

The catalogue preserves the documented board-level surface without presenting a talk summary as a complete hardware specification, manufacturing record, safety assessment, or reproducible design.

Source note: The 2025 BSides Knoxville Badge: Tips, Tricks, and Tribulations public AllBSides mirror/transcript.

BugCON 2023 Badge note

hardware variant evidence caveat · README and repository tree · documented with caution

The README describes ESP32S3 or RP2040, the tree exposes an ESP32-S3 KiCad design, and the second hardware path is named SAMD11 even though its schematic symbol and properties identify RP2040 hardware.

Hardware claims stay tied to visible source files rather than inferring which variant shipped, how many boards were produced, or whether every tree name matches the final production board identity.

Source note: BugCON 2023 README, ESP32-S3 schematic, SAMD11-named RP2040 schematic, and repository tree.

DC-34 Countdown to Singularity Badge note

hardware, 9 V power, SAO, assembly, and electrical-safety specification boundary · public README, BOM, and native board tree · design sources published; final engineering validation unrecovered

The source names ATmega328P, PCF8523T, displays, regulators, a 9 V path, buttons, seven SAO connectors, and an ISP port, but does not establish a final schematic/BOM revision, board stack-up, display wiring/current, power-source compatibility, regulator dissipation/thermal behavior, battery/connector quality, voltage/current budgets, SAO version/pinout/limits, ESD/short/reverse protection, assembly/inspection/test protocol, measured behavior, compliance, enclosure, or a safe-use result.

The record links a real design trail without presenting it as a complete electrical specification, a validated battery/adapter recommendation, a universal SAO compatibility claim, a safe assembly guide, or a manufactured quality record.

Source note: DC-34 Countdown to Singularity README, BOM, and public KiCad board tree.

Ouroboros Badge (DEF CON 34) note

hardware, AA power, enclosure, and safety documentation gap · maker product description · high-level physical claims published; engineering documentation absent

The source names a CH32V003, twelve LEDs, exposed circular single-layer PCB, no protective enclosure, and two AA batteries, but does not publish a schematic, BOM, PCB/Gerbers, dimensions, battery chemistry, current/voltage limits, regulator/protection design, connectors, thermal/fault testing, assembly procedure, runtime measurement, safety guidance, or compliance evidence.

The record does not turn a maker-described bare board and battery arrangement into a safe-use instruction, a battery-life guarantee, or a universal hardware-compatibility claim.

Source note: Ouroboros Badge #BadgeLife product page.

Hacker Pager (DEF CON 34 Revision) note

hardware, LiPo, USB-C, RF, and mechanical safety boundary · official project site and public design repositories · source-published components/design files; engineering validation unrecovered

The sources name ESP32-S3, SX1262, LCD, LEDs, microSD, USB-C, LiPo, battery management, radio bands, antenna wording, resin/acrylic construction, and public design files. They do not establish the exact 2026 board/case revision, full schematic/BOM verification, battery cell/protection/charger settings, power/current/thermal budgets, port protection, RF antenna characterization, emissions/compliance, mechanical load/drop testing, assembly inspection, repair procedure, final quality control, or safe modification/use result.

The record provides the documented hardware surface without becoming an electrical, radio, battery, fabrication, or repair endorsement.

Source note: Hacker Pager official project site plus Exploitee.rs electronics and case repositories.