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)
Unknown Security Conference 2026 Pwn Llama Badge note

delivery and allocation boundary · official pass copy plus public hardware archive · recipient evidence incomplete

The official pass says it includes a lanyard plus official badge, while the public repository documents an electronic badge design. Neither source identifies final unit count, which pass holders received the electronic device, color or hardware variants, or completed distribution.

The badge is documented as a real event-specific electronic design without claiming universal attendee issue or any final delivery outcome.

Source note: UnknownCon 2026 event page and ElectronicCats Badge-UnknownSecurity-Conference-2026 README.

BSides Kristiansand 2026 Shield Badge note

delivery logistics caveat · post-event account · documented narrowly

The published post-event account reports tight deadlines, logistical challenges, and cross-continent transport before saying the programmed, flashed, and tested badges arrived in time. It does not specify a late shipment, defect, attendee impact, or a production failure.

The entry preserves a real delivery constraint without overstating it as a failed distribution or hardware-quality incident.

Source note: The Story Behind the BSides Kristiansand 2026 Shield Badge post-event account.

JawnCon 0x3 Calculator Badge note

design and firmware archive gap · official badge page · BOM, manual, and firmware image published; schematic, PCB, and firmware source absent

JawnCon publishes the bill of materials, manual, case files, and since October 17, 2026 a firmware HEX image, but no schematic, PCB files, firmware source, or badge designer credit, and the case files are marked © 2026 JawnCon, LLC without a reuse licence.

The record cites the official manual for behaviour and the HEX image for its strings, and leaves circuit details beyond the BOM, firmware source, and reuse rights open.

Source note: JawnCon badge and case printing pages and jawncon-badge.hex, checked 2026-10-21.

NYC Badge (DEF CON 34) note

design, firmware, and license archive gap · primary storefront and maker-profile sources · needs public archive or terms

The public listing provides a component-level kit description but no schematic, BOM, Gerbers, board source, firmware repository or binary, flashing guide, protocol description, hardware license, software license, or documentation license.

The record can describe the listed components and pre-flashed-controller statement without claiming reproducible hardware, inspectable firmware, update support, or reusable design files.

Source note: Uberflux NYC Badge listing and buck maker profile.

BSides Orlando 2026 Electronic Badge note

design-credit and distribution-role gap · official organization and public repository review · named designers and organization credited; manufacture and fulfillment roles not recovered

The rev R1 schematic title block names Kevin Colley, whose commits carry the August 4 microcontroller addition through the September 1 production files, while Jose Rodriguez authored the August 4 initial discrete-LED design whose Jose_3mm_Led library symbols survive in the retained blink LEDs. The organization profile establishes Security BSides Orlando as publisher, but the reviewed public material does not name a manufacturer, assembler, funder, or distribution owner, and the repository predates any stated official event-page badge announcement.

The catalogue credits the title-block designer, the initial-design author, and the organization without assigning manufacturing, artwork-ownership, or fulfillment responsibility beyond what the public sources state.

Source note: hardware/bsidesorl-v1.kicad_sch title block, repository commit authors, and Security BSides Orlando GitHub organization profile.

MNSEC 2026 Event Badge note

design-file and licence gap · repository contents · documentation-only archive

Unlike the BSD 2-Clause MNSEC2025BADGE archive, the 2026 repository contains only a user-guide PDF and two renders, with no licence, schematic, Gerber, BOM, or firmware; the module and display identification comes from the render silkscreen rather than a parts list.

Hardware claims stay at the level visible in the guide and renders, and the 2025 licence is not carried over to the 2026 material.

Source note: helicopteresdc MNSEC2026BADGE repository file listing, checked 2026-09-29.

Friend or Foe Badge (DEF CON 34 Packet Hacking Village) note

detection, privacy, security, software-release, and operational-use boundary · maker repository documentation and Android release notes · high-level RF and software behavior documented; Android companion release published; validation and operating terms unrecovered

The public project describes passive BLE/Wi-Fi/Remote ID-oriented awareness, Android-over-USB-C controls, and published source/version labels. The maker's v0.67.18 Android release documents nearby-list, distance-gating, location-refresh, and Bluetooth/Privacy-list changes, but explicitly retains physical-phone Bluetooth and field-location testing. Reviewed sources do not establish detection accuracy, false-positive/false-negative rates, target identification, range, location accuracy, lawful deployment, notice/consent, data-minimization or retention terms, authentication, encryption, threat model, security review, release-to-unit firmware mapping, recovery support, or a final event firmware manifest.

The record avoids converting a project description or companion release into surveillance guidance, an identification claim, a privacy/security assurance, a supported update process, or a guarantee of behavior on any deployed badge.

Source note: Friend or Foe README, public repository, and v0.67.18 Android release, reviewed 2026-09-16.

AND!XOR DC28 Badge note

distributed-drop caveat · project-owner source but incomplete · documented as unofficial badgelife

The project page says badges would be shipped to drops around the country for proxy hackers to give away for free, but this pass did not recover a final drop manifest, production count, recipient list, or universal-attendee distribution statement.

The catalogue treats the board as an unofficial DEF CON-adjacent badgelife artifact and avoids implying it was the official DEF CON 28 admission badge or a universally issued attendee item.

Source note: AND!XOR DC28 Hackaday.io project page and RTFM log.

BSides Dublin 2026 Harp Badge note

distribution and authorship gap · source-conservative public record · needs primary attribution or quantity record

The organizer-owned archive and organizer updates prove a real 2026 Harp Badge, but the recovered public sources do not name the badge designer or give a production/distribution quantity.

The dossier does not infer designer credit, attendee allocation, or production scale from the technical archive alone.

Source note: BSides Dublin organizer updates and HardwareBadge2026 repository.

HITCON CMT 2018 HITCON Wallet Badge note

distribution and original-badge caveat · primary source · documented

HITCON describes the Wallet badge as limited to Royal VIP and Premium Pass holders, and KKTIX says the electronic badges could not be used for verification, registration, or lunch pickup because attendees still needed the original badge.

The record distinguishes the Wallet electronic board from the regular conference credential and avoids implying universal attendee distribution.

Source note: HITCON CMT 2018 events and KKTIX ticketing pages.

BSides Knoxville 2025 Fox Pick ESP32-S3 Badge note

distribution and production boundary · official guide plus public maker talk · artifact and maker relationship documented; allocation unresolved

The official guide says Fox Pick made the badges, and the public talk discusses high-volume manufacture, but neither reviewed source gives an exact unit count, recipient list, ticket tier, pickup record, variant inventory, replacement policy, or attendee-wide allocation statement.

The record documents a real event-linked electronic artifact without treating the existence of badges or a manufacturing account as proof that every attendee received the same finished device.

Source note: BSides Knoxville 2025 official guide and Morgan Rogers' public Fox Pick talk.

BSides Cleveland 2026 Cassette Badge note

distribution and quantity gap · organizer repository and official event page · design and fabrication documented; handoff unpublished

The writeup says PCBWay fabricated, printed, and assembled the units and the official page marks the event completed, but no source states how many attendee or volunteer badges were made, whether every attendee received one, or whether the files are the exact production revision.

The record treats the badge as a real event artifact without asserting attendee-wide allocation or a unit count.

Source note: BSidesCLE/Badge-2026 writeup and the BSidesCLE 2026 conference page, checked 2026-10-15.

SAINTCON 2026 Planned Electronic Badge note

distribution and variant boundary · official 2026 sources · planned

The sponsor prospectus distinguishes Electronic Badge and Non-Electronic sponsor tickets, and the CFP identifies a Speaker MiniBadge, but the public sources do not establish final general-attendee allocation, production quantity, universal badge type, variant inventory, or main-badge designer attribution.

The record preserves documented sponsor and speaker paths without treating them as proof of every attendee's final conference artifact.

Source note: SAINTCON 2026 Sponsor Prospectus and Call for Papers.

cackalackycon 2026 Speaker Electronic Badge note

distribution and variant boundary · organizer-provided CFP and ticketing · partially source-backed

The CFP establishes selected-speaker eBadge allocation, a paper guest admission, and a paid guest eBadge condition, but does not show whether the speaker-colored badge differs technically from paid-ticket badges, what speaker-colored means physically, or how many general attendees received an electronic badge. The Eventzilla marketing line does not resolve those boundaries.

The record preserves the documented speaker and guest paths without claiming a universal attendee eBadge, a known variant inventory, or a visual color treatment.

Source note: cackalackycon 2026 CFP and organizer-linked Eventzilla ticketing page.

BSides Nashville 2026 Challenge Coin note

distribution and variant boundary · official promise and organizer-feed corroboration · attendee receipt corroborated; full ledger unavailable

The official page promises a coin for every attendee, and the official organization feed re-shares an attendee report of coins. The reviewed sources do not publish attendance count, production count, handout ledger, no-show handling, replacements, lost-item support, individual receipt evidence, or any coin variants.

The record can distinguish a documented conference-wide promise and a corroborated attendee report from a complete fulfillment or variant inventory claim.

Source note: What's New for BSides Nashville 2026 and BSides Nashville organizer updates.

ROOTCON 20 Electronic Badge note

distribution scarcity · official pre-event guide · post-event split unpublished

The RC20 guide says electronic badges are first-come at on-site check-in while supplies last and that Type-B badges are the fallback. The September 28 post-event drop publishes the Human-tier firmware but no production count or statement of how many attendees received the electronic badge.

The record does not imply every attendee received the electronic version.

Source note: ROOTCON 20 con-goers guide and media-server drop.

CyberThreat 2024 Hackable Badge note

distribution scope caveat · official event page · documented source limitation

The official page proves hackable badges at CyberThreat 2024 and describes in-person delegate hands-on opportunities, but does not publish exact badge quantity, ticket-tier eligibility, or whether every on-site attendee received one.

The catalogue records the badge as a CyberThreat 2024 challenge artifact without inventing a universal distribution count.

Source note: CyberThreat official event page.

BSidesKC 2019 Conference Badge note

distribution scope caveat · badge-maker writeup · documented

Badge Pirates says only 250 preregistration attendees received electronic badges, organizer/speaker/volunteer/Jr Hacker batches totaled 128 hand-assembled boards, and non-electronic participant PCBs carried crypto-challenge clues.

The catalogue avoids implying every BSidesKC attendee had a fully electronic badge while still recording the verified electronic badge ecosystem.

Source note: Badge Pirates BSidesKC 2019 badge writeup.

HITB+CyberWeek 2021 Packet Hack Badge note

distribution scope caveat · artifact source but incomplete event logistics · documented source limitation

The public badge sources tie the Packet Hack Badge to HITB+CyberWeek and Packet Hack Village, but do not document exact attendee eligibility, distribution count, or whether it was issued to all conference attendees.

The record is treated as a Packet Hack Village / HITB+CyberWeek artifact rather than a universal admission credential.

Source note: Hackster Packet Hack Badge project and HITB+CyberWeek event sources.

Seasides 2026 Roulette Badge note

distribution, participant-count, and recipient-scope caveat · separate official and maker statements · planned availability and maker-reported live assembly; final ledger unrecovered

HW101 said there would be enough badges for everyone attending, while the maker README says more than 300 participants assembled the Roulette design live. Neither source supplies a final production count, serial/recipient ledger, independent attendee pickup report, relationship between the two quantities, excluded cohorts, leftovers, replacements, or evidence that all attendees received the same design/revision.

The record preserves both distribution-related statements without converting them into a confirmed universal issuance count or individual fulfillment history.

Source note: HW101 Hardware Hacking Village page and Rahul Thareja's commit-pinned Roulette Badge README.

Open Sauce 2026 Badge note

distribution, purchase, and physical-handoff gap · post-event designer and attendee archives · physical badge use corroborated; recipient and purchase outcome unrecovered

The sources establish that physical badges and an eyebrow module were present during the festival, and the designer README has a future purchase-link note. They do not establish ticket eligibility, price, inventory, production quantity, registration handoff, recipient count, standard-versus-optional configurations, order history, shipment, completed sale, replacement, refund, or attendee-wide allocation.

No participant count, entitlement, price, purchase result, or universal issuance is inferred from a public source archive or a single attendee project's account.

Source note: Open Sauce official tickets; calebmarting README; putnam custom-firmware README.

BadgESC{21} Badge note

distribution, recipient, and event allocation boundary · organizer repository wording · badge described as distributed; allocation record unrecovered

The organizer repository explicitly says the flex-PCB badge was distributed at ESC{21}, but the reviewed public sources do not state how many were made, which ticket or role received one, whether every attendee was eligible, what variants existed, who collected one, whether units were retained, or the final delivery outcome.

The catalogue calls this a completed event artifact without turning a distribution statement into an attendee-wide entitlement, precise production number, recipient ledger, or uniform delivery claim.

Source note: End Summer Camp badge-2025 repository and 2025 event registration.

Hackers Teaching Hackers 2026 Eagle 5 Badge note

distribution, ticket, and attendee-handoff gap · official event and post-event archive sources · event complete; allocation outcome unrecovered

Official HTH sources establish that the June 3-5 conference occurred, and a public attendee account says a light-up badge was part of the CTF. No reviewed source establishes ticket eligibility, badge price, production quantity, inventory, role variants, recipient count, registration pickup, shipment, replacement, refund, attendee-wide allocation, or individual physical receipt of the Eagle 5 hardware.

The entry does not turn a public source archive or one attendee account into a distribution record or a claim that every conference participant received the same badge.

Source note: HTH official site and LinkedIn updates; Paul Danis public account; Eagle 5 source repository.

Maritime Hacking Village DC33 Differential Destroyer note

distribution-count caveat · source-backed but incomplete · needs shipped-count recovery

The README documents boards sold through the village and bundled with a flashed Pico 2, while OSHWA identifies the board as the official Maritime Hacking Village DEF CON 33 badge; this pass did not recover a public shipped count, sale quantity, or full distribution report.

The badge is included as a source-backed village badge without claiming attendee-wide DEF CON distribution or a final production quantity.

Source note: OSHWA certification and Differential Destroyer README.

HackConRD 2024 ATTiny85 Badge note

distribution-depth caveat · badge-team source but no ticket archive · needs event archive recovery

The recovered 2024 source trail proves an official HackConRD badge and event-specific firmware, but does not expose a ticket-tier archive, final production count, pickup process, or post-event attendee guide.

The record states first official badge and technical archive details without claiming attendee-wide distribution mechanics or quantity.

Source note: Verpent HackConRD 2024 writeup and HHW_HackConRD2024 repository.

Area41 2026 ESP-Based Electronic Badge note

distribution-detail gap · official event page and organizer recap · event complete; badge allocation detail remains absent

The official page promised a badge for each attendee, while the recap reports 600 attendees and more than 300 SAO extension solderings. Neither source supplies a badge-specific production or handoff ledger, variant inventory, extension distribution, or individual contributor list.

The record preserves documented event outcome and maker credit without converting aggregate event activity into an exact main-badge count, universal add-on allocation, or complete authorship roster.

Source note: Area41 Conference 2026 official page and AREA41 2026 organizer recap.

DC503 DEF CON 26 VIP Banglet note

distribution-scope caveat · source-backed but incomplete · needs final handout record

The repository title says VIP Banglet and the sources prove a real badge project, but this pass did not recover a final quantity, party guest list, sales record, or attendee-wide distribution statement.

The record avoids claiming universal DEF CON, DC503, or BSidesPDX distribution and treats the artifact as a VIP/party wrist badge.

Source note: pdxbadgers/2018-banglet repository and README.

DC503 5ohBEE Pager note

distribution-scope caveat · source-backed but incomplete · needs final handout record

The repository proves a real 503 Party 2019 pager project, but this pass did not recover a final quantity, recipient list, sales record, or attendee-wide distribution statement.

The record avoids claiming universal 503 Party, DC503, DEF CON, or RainSec distribution and limits itself to the public repository's party-pager scope.

Source note: pdxbadgers/5ohBEE-2019 repository metadata and commit history.

BIC Village DC33 BIC Pick Badge note

distribution-scope caveat · official page plus event summary · documented

Public sources say BIC Picks were worn by village volunteers, leaders, and supporters, were available through limited purchase or trade at DEF CON 33, and later sold out with merchandise, but they do not state a final badge count or attendee-wide distribution.

The record preserves the verified distribution language without implying every DEF CON or BIC Village attendee received one.

Source note: BIC Pick badge page and B.I.C. Village Event 2025 @ DEF CON 33 PDF.

BSidesPDX 2015 Badger Badge note

distribution-scope caveat · official schedule plus repositories · documented

The official source proves a Badger Hacking workshop and the repositories prove public 2015 Badger PCB/firmware archives, but this pass did not recover a production count, attendee-wide distribution statement, ticket tier, or final handout logistics.

The catalogue models the artifact conservatively as a BSidesPDX 2015 badge-hacking board archive rather than a universal attendee badge claim.

Source note: BSidesPDX 2015 schedule, pdxbadgers/pcb-2015, and pdxbadgers/fw-2015.

BSidesPDX 2016 ATTiny85 Badge note

distribution-scope caveat · secondary event listing plus repository · documented

Calagator says PCB badges would be given away with donors prioritized, and the repository proves a public PCB badge archive, but this pass did not recover an attendee-wide distribution statement, final quantity, assembly note, donor-tier rule, or handout ledger.

The catalogue records the source-backed BSidesPDX 2016 PCB badge without claiming that every attendee received one.

Source note: Calagator Security BSides Portland listing and pdxbadgers/pcb-2016.

BSidesPDX 2017 BMD-300 Badge note

distribution-scope caveat · official schedule plus repository · documented

The official schedule and speaker page prove a 2017 BSides PDX badge existed and had an Ox-Vox add-on target, while the repository proves a badge hardware archive, but this pass did not recover an attendee-wide distribution statement, production count, assembly note, or final handout logistics.

The catalogue records a source-backed BSidesPDX 2017 badge archive without overclaiming distribution scope.

Source note: BSidesPDX 2017 schedule, speakers page, and pdxbadgers/pcb-2017.

BSidesPDX 2018 ATTiny861 Badge note

distribution-scope caveat · official schedule plus repository · documented

The official schedule and speaker page prove a badges-related BSidesPDX 101 session and the repository proves a badge archive, but this pass did not recover an attendee-wide distribution statement, quantity, assembly note, or final handout logistics.

The catalogue records a source-backed BSidesPDX 2018 badge archive without overclaiming distribution scope.

Source note: BSidesPDX 2018 schedule, speakers page, and pdxbadgers/badge-2018.

BSidesPDX 2019 Multnomah Badge note

distribution-scope caveat · official schedule plus repository · documented

The official schedule proves a badges-related BSidesPDX 101 session and the repository proves a badge archive, but this pass did not recover an attendee-wide distribution statement, quantity, assembly note, or final handout logistics.

The catalogue records a source-backed BSidesPDX 2019 badge archive without overclaiming distribution scope.

Source note: BSidesPDX 2019 schedule and pdxbadgers/badge-2019.