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)
DEF CON 28 Safe Mode Badge note

audio-artifact caveat · source-backed but incomplete · needs deeper artifact inventory

Public sources document the cassette, liner, lanyard, and media-server availability, but this pass does not mirror or audit every audio file, transcript, tape variant, or final puzzle solution branch.

The catalogue records the verified analog badge surfaces and leaves complete audio forensics for a later artifact-level pass.

Source note: DEF CON forum challenge post, Hackaday hands-on article, and CIRCUITS TO KERNEL writeup.

ICS Village DEF CON 34 Badge note

availability and distribution boundary · primary official sources · scheduled DEF CON 34 dates elapsed; distribution outcome unconfirmed

FREE-WILi says the badge will be available on-site at ICS Village or Vendor Village while supplies last, and the official ICS Village page announced the August 6-9, 2026 event. DEF CON's official news confirms the host conference wrapped on August 10, 2026, but the rechecked village and FREE-WILi pages still read pre-event and do not establish a completed badge run, recipient count, attendee-wide issue, price, sold-out status, or fulfillment outcome.

The catalogue records announced badge availability, not delivered hardware, a universal attendee allocation, or observed event use.

Source note: ICS Village DEF CON 34 Badge page, official ICS Village DEF CON 34 page, and DEF CON's official wrap-up news, rechecked 2026-09-23.

CypherCon 2026 Extreme Badge note

availability, fulfillment, and benefit boundary · official registration, FAQ, and ticket category · recovered sold-out listing; completed recipient outcome unavailable

The recovered official listing labels the Extreme Badge sold out and its premium copy lists event experience benefits, but the sources do not establish quantity, purchaser count, payment, allocation, final price, eligibility, collection, shipment, replacement, receipt, benefit delivery, badge inventory, or whether every Extreme purchaser received an electronic artifact. The event's completion does not resolve any of those outcomes.

The catalogue records the organizer's availability and premium-tier wording, not a fulfilled VIP benefit, a guaranteed badge allocation, a final stock ledger, or an admission/access entitlement beyond the source's high-level ticket description.

Source note: CypherCon 2026 registration, ticket category, FAQ, and public organizer-account timeline mirror.

BSides Lisbon 2026 Electronic Badge note

badge and CTF relationship boundary · official current About page · both programme items announced; linkage unproven

The About page lists an electronic badge and a CTF in the same programme sentence, but does not say the CTF is physical, badge-based, or implemented by the badge. The 2026 badge page instead describes its own badge competition across both days. No challenge mechanics, source, scores, data flow, prizes, or results are public for either.

The catalogue records the CTF and the badge competition as separate official programme elements without presenting the badge as a CTF device or asserting how the competition works.

Source note: BSidesLisbon 2026 About and badge pages, checked 2026-10-21.

Laser* Tag Badge DS (DEF CON 34) note

badge firmware and design archive gap · official maker page and public protocol repository · needs final badge archive

OpenLASIR is a public MIT-licensed compatibility protocol with examples, but reviewed sources do not publish complete final DS firmware, a badge-specific flashing workflow, schematic, PCB files, Gerbers, BOM, electrical design details, or a complete badge firmware license.

The catalogue can distinguish documented interoperability and game intentions from unverified full-badge implementation or reproducible-build claims.

Source note: OpenLASIR repository and Dani Weidman official maker page.

BSides Greenville 2023 Wi-Fi Analyzer Badge note

badge form, distribution, and credential boundary · event-programme wording and attendee report · event-linked badge documented; form and allocation unresolved

The source material calls the starting item a conference badge and says it could be transformed, but does not establish whether it was electronic before conversion, whether it was a PCB, whether an add-on was supplied, who could participate, ticket-tier eligibility, badge quantity, component-kit count, completed build count, replacement policy, or whether it operated as an admission credential.

The record remains a source-backed event artifact rather than an unsupported universal-attendee, access-control, or electronic-hardware claim.

Source note: CyberSC's BSides Greenville 2023 listing and Mike Holcomb's contemporaneous BSidesGVL announcement.

Carolina Code Conference 2026 Circuit Board Badge note

badge rendering and visual-rights boundary · official announcement image review · official renders visible; local reuse not cleared

The organizer's badge announcement displays renderings of the planned green and purple circuit-board badges, but the page does not provide an image-specific reusable license or explicit local-publication permission, photographer/render author attribution, processing basis, or final physical-artifact identity. It also depicts a planned rather than confirmed delivered object.

No local badge image is published; the record remains source-backed and image-free pending a factual artifact image or official upstream raster with complete reuse basis, attribution, and processing provenance.

Source note: Carolina Code Conference 2026 Circuit Board Badge announcement and badge.gallery image policy.

Hack Glasgow 2026 Attendee Name Badge note

badge technology, access-control, and data boundary · official FAQ review · no technical or badge-linked data behavior published

The official FAQ says a valid QR code is scanned on entry and separately says a handle or name may be written on a badge. It does not connect those statements or publish a badge barcode/QR, RFID/NFC, chip, firmware, app, protocol, identity system, data collection, privacy notice, retention, account linkage, CTF behavior, repository, or security review.

The entry does not turn the event's admission procedure into a technical feature, access-control claim, or data-handling claim about the attendee name badge.

Source note: Hack Glasgow official 2026 FAQ and event page.

BSides Newcastle 2025 Space Badge note

badge-sponsor relationship, allocation, and handoff boundary · official event recap, Punk sponsor listing, and maker archive · completed event and sponsor badge documented; recipient scope unrecovered

The official recap reports 200 checked-in participants, Punk Security identifies itself as badge sponsor, and its archive identifies the Space Badge for the event. The reviewed sources do not give a production count, ticket-tier eligibility, role allocation, recipient list, pickup/handoff record, replacement policy, or proof that all 200 checked-in participants received the badge.

The catalogue records a completed event-associated electronic badge without turning sponsorship or attendance totals into a universal allocation claim.

Source note: BSides Newcastle 2025 official recap; Punk Security event listing; Space Badge repository.

CSIDES 2025 Crab Badge note

badge-sponsor relationship, allocation, and handoff boundary · official organizer sources, Punk sponsor listing, and maker archive · completed event and sponsor badge documented; recipient scope unrecovered

Organizer sources establish the completed October 3 Grand Pier conference, Punk Security identifies itself as badge sponsor, and its archive identifies the Crab Badge for the event. The reviewed sources do not give a production count, ticket-tier eligibility, role allocation, recipient list, pickup/handoff record, replacement policy, or proof that all conference attendees received the badge.

The catalogue records a completed event-associated electronic badge without turning sponsorship or attendance evidence into a universal allocation claim.

Source note: CSIDES sponsors page and Eventbrite listing; Punk Security event listing; Crab Badge repository.

BSides Bournemouth 2025 Skull Badge note

badge-sponsor relationship, allocation, and handoff boundary · official event context, Punk sponsor listing, and maker archive · completed event and sponsor badge documented; recipient scope unrecovered

The official event page reports 200+ attendees, Punk Security identifies itself as badge sponsor and advertises skull badges, and its archive identifies the Skull Badge for the event. The reviewed sources do not give a production count, ticket-tier eligibility, role allocation, recipient list, pickup/handoff record, replacement policy, or proof that all reported attendees received the badge.

The catalogue records a completed event-associated electronic badge without turning sponsorship or attendance evidence into a universal allocation claim.

Source note: BSides Bournemouth 2025 official page and Security BSides listing; Punk Security event listing; Skull Badge repository.

BSides Exeter 2025 Pirate Ship Badge note

badge-sponsor relationship, allocation, and handoff boundary · official event sources, Punk sponsor listing, and maker archive · completed event and sponsor badge documented; recipient scope unrecovered

The organizer sources establish the completed April 26 conference, Punk Security identifies itself as badge sponsor, and its archive says the Pirate Ship Badge was given out at BSides Exeter. The reviewed sources do not give a production count, ticket-tier eligibility, role allocation, recipient list, pickup/handoff record, replacement policy, or proof that all attendees received the badge.

The catalogue records a completed event-associated electronic badge without turning sponsorship or a broad maker distribution statement into a universal allocation claim.

Source note: BSides Exeter 2025 organizer ticket page and Security BSides listing; Punk Security event listing; Pirate Ship Badge repository.

BSides Lisbon 2026 Electronic Badge note

badge-team role and allocation boundary · official team and programme pages · team-section credit available; work scope and recipients unreleased

The current team page lists Pedro Umbelino under Badge, and the badge page says kripthor developed the conference badge once again and names Bitsight as sponsor. The pages do not connect the two names, and none identifies hardware, firmware, manufacturing, security review, support, licensing, or the final recipient scope.

The team listing, the kripthor development credit, and the sponsor are recorded separately without claiming who built which part or which attendees receive the badge.

Source note: BSidesLisbon 2026 Team, About, and badge pages, checked 2026-10-21.

BSides Las Vegas 2026 Participant Badge note

badge-type, allocation, and credential boundary · official current registration, ticketing, and CFP sources · documented badge categories; individual allocation unverified

Official sources distinguish participant, donor, volunteer, speaker/mentor, and special conference badge paths, while also describing a participant badge for a speaker or mentor's designated plus-one. They do not publish a recipient ledger, final count, transfer policy for all badge types, exact privilege matrix, pickup confirmation for a named person, or a design/specification tying every category to one physical artifact.

The record describes the participant badge and its documented access context without treating every 2026 badge label as identical, universally issued, or an interchangeable DEF CON credential.

Source note: BSides Las Vegas 2026 Registration Information, Humanitix ticketing, Volunteer Guide, and CFP.

Hack the North 2026 Hacker Badge low

battery heat and travel safety · official attendee manual · documented safety guidance

The official manual tells hackers to switch the badge off immediately and bring it to the Badge Help Desk if the top, back, or left side near the USB port feels warm, to remove the batteries if it is very hot or damaged, to switch it off before connecting USB, and to remove the batteries before flying. Low batteries are also named as the usual cause of glitches.

Owners reusing the badge should follow the same power and battery precautions; the manual does not report any specific incident.

Source note: hackthenorth/badge-firmware docs/BADGE-MANUAL.md, checked 2026-10-15.

Spectre Sniffer Badge (DEF CON 34) note

battery, EMF, and electrical-safety boundary · primary maker listing · needs technical and safety documentation

The maker names a protected 18650 battery and a live EMF detector, but publishes no cell capacity/identity, charge or protection implementation, current/thermal data, fault behavior, replacement procedure, safety certification, sensor identity, calibration, accuracy, interference behavior, or usage limits.

The catalogue does not turn the seller's protected-battery and EMF language into a safety endorsement, electrical-service guide, calibrated-instrument claim, or paranormal-detection claim.

Source note: Spectre Sniffer Badge listing.

Shitty Kitty V2 (DEF CON 34) note

battery, charging, and modification safety boundary · primary maker storefront source · needs operating and safety documentation

The maker lists LiPo power, battery-management components, thermal monitoring, a buck-boost supply, and fast-charging support, plus a polycarbonate battery enclosure. It does not publish cell make/model, charge-current configuration, temperature thresholds, fault behavior, battery replacement procedure, current limits, safety guidance, certification, or modification instructions.

The record does not convert component names or marketing language into an electrical-safety endorsement, battery-service guide, or safe-modification claim.

Source note: Uberflux Shitty Kitty V2 product listing.

Gothcon 2026 Blinky Badge note

battery, charging, and modification safety boundary · primary organizer store and public repository · needs operating and safety documentation

The store names a 2,000 mAh LiPo and USB-C recharging with overcharge protection, while the source tree supplies firmware and board files. Neither reviewed source publishes battery cell identity, charge settings, thermal/current measurements, fault behavior, battery replacement procedure, safety certification, or a safe-modification guide.

The record does not transform source component claims into an electrical-safety endorsement, battery-service procedure, or sanctioned repair/modification instruction.

Source note: Gothcon Badge Store listing and gothcon-firmware repository.

Celestial Wayfinder Badge (DEF CON 34) note

battery, charging, and modification safety boundary · maker listing, firmware README, and CAD repository · needs final operating and safety documentation

Sources describe a Li-ion/18650 power path, USB-C charging/updating, TP4056 on early revisions, BQ25672 on v3, and 3D-printed mechanical modifications. They do not publish cell identity/capacity for the offered unit, charger settings, protection test results, current/thermal data, replacement procedure, certification, fault behavior, safe printed-material guidance, or a sanctioned modification process.

The catalogue does not turn public power or CAD material into a battery-service guide, electrical-safety endorsement, charging claim, or safe-modification authorization.

Source note: Celestial Wayfinder listing, firmware README, and Wayfinder-CAD README.

SAO Many SAOs Badge (DEF CON 33) note

battery, charging, multi-SAO power, and host-safety documentation gap · maker high-level README · power claims documented; engineering validation absent

The README names two 18650 batteries, USB/barrel paths, stated 30 mA and 300 mA conditions, and surge protection, but does not publish cell chemistry/brand/protection, battery holder, charging/power-path circuit, fuse ratings, regulator design, input voltage limits, per-port power allocation, inrush, thermal, short-circuit, reverse-polarity, ESD, fault, battery-transport, or host-compatibility tests.

The record does not convert a high-level power-budget statement into a battery-safety instruction, a guaranteed power supply, or a safe multi-SAO integration certificate.

Source note: DC33-SaO-MANY-SAOs README and product page.

Monorail Con Badge (DEF CON 34) note

battery, power, and SAO host-compatibility gap · official high-level product description · needs technical and safety documentation

The product names two AAA batteries, a regulated 3.3 V supply, and a Sphere SAO claimed to work with upside-down SAO ports, but provides no voltage/current envelope, battery-holder details, power path, polarity/short protection, runtime, thermal data, charging/transport guidance, pinout, electrical test result, or supported-host matrix.

The catalogue preserves the seller's limited power/SAO statements without treating them as safe-use instructions, universal host compatibility, a battery-safety endorsement, or an electrical specification.

Source note: Zach's Hacks product page.

Helgatchi Badge (DEF CON 34) note

battery, power, antenna, radio, and safety documentation gap · maker component-level claims · needs final engineering documentation and testing

Public sources identify a 400 mAh 3.7 V LiPo, XIAO ESP32-S3, LCD, LEDs, vibration motor, and an external 2.4 GHz antenna path, but do not provide charger/protection circuit details, battery vendor/specification, current draw/runtime, USB power behavior, fusing, voltage/current limits, antenna gain/matching, RF emissions/compliance, enclosure/fire/drop testing, environmental limits, user warnings, or safety/compliance evidence.

The record retains source-named components without presenting the badge as electrically complete, radio-compliant, safe to charge/carry, or suitable for every configuration.

Source note: DC801 Helgatchi Badge product page and Pips801/Helgatchi repository.

39C3 Critical Decentralization Cluster Badge warning

beta firmware, sensitive-data, and security-critical-use boundary · public firmware README · public source explicitly pre-1.0 beta

The later public CDC Badge OS README states that flashing can wipe stored FIDO2/U2F credentials, TOTP seeds, password-vault entries, GPG keys, and PIN data; it calls the project a proof of concept/demonstrator and says not to use it as-is for production or security-critical deployments.

The record may describe the public software capability surface but does not endorse the firmware, vouch for its cryptography, privacy, data durability, or safety, or imply it was the software deployed at 39C3.

Source note: krim404/cdc-badge-os README.

Aerospace Village DC33 ADS-B Badge note

build and USB caveat · primary docs · documented

The build guide requires a Linux machine tested on Ubuntu 22.04 and 24.04 and warns the Buildroot build can take around an hour and a half; the FAQ also documents Windows, macOS USB-C, Wi-Fi, SSH, keyboard, and battery-reset caveats.

The record presents Winglet OS as publicly buildable and hackable while making clear that toolchain, USB, and access workflows are not frictionless for every host.

Source note: Building Winglet OS guide and AV Badge FAQ.

Hackaday Remoticon.2 DIY Badge note

builder-completion caveat · primary project and Hackaday article · documented

Public sources describe the badge as a PCB canvas with space for builders to add their own electronics, including a MicroMod variant, rather than a complete stock electronics-and-firmware package.

The record avoids inventing a fixed MCU, app set, puzzle, or firmware behavior for the base Remoticon.2 template.

Source note: Hackaday article, Hackaday.io project description, file list, and project logs.

BSides Roanoke 2026 Participant Badge Challenge note

challenge integration gap · self-identified challenge source · needs challenge walkthrough

ShenLabs explicitly identifies itself as a BSides Roanoke 2026 badge challenge, but no reviewed source explains how the participant badge connected to the web puzzle, its clues, a QR/URL/credential mechanism, a solution, or any reward path.

The catalogue can document the declared challenge companion without claiming that it was firmware, a badge-hosted application, or a particular physical interaction.

Source note: ShenLabs footer and reviewed BSides Roanoke / organizer ticketing sources.

Wordweaving Badge (DEF CON 34) note

challenge, multiplayer, privacy, and behavior boundary · official maker pages · marketing-level behavior only

The project page and listing differ between 30-plus and 35-plus CTF/puzzle wording and make high-level multiplayer/link-up/word-building claims. They do not publish final challenge inventory, spoilers policy, rules, score validation, pairing/transport protocol, range, player-data handling, threat model, privacy/security review, accessibility details, event support, or a stable behavior contract.

The catalogue preserves the game and collaboration claims without inventing a final challenge count, protocol, network/privacy guarantee, completed event experience, or solution material.

Source note: BigTaro Wordweaving project page and Uberflux product page/payload.

DEF CON 29 Badge note

challenge-artifact caveat · source-backed but incomplete · needs deeper artifact inventory

Public sources document hardware, firmware updates, SAO/IR hints, serial/Morse material, and solving paths, but this pass does not mirror or audit every firmware image, forum attachment, add-on, or final badge state.

The catalogue records the verified hardware and challenge surfaces while leaving full artifact preservation for a later pass.

Source note: DEF CON forum badge-hacking thread, Hackaday hands-on article, and Science Viking Labs writeup.

DEF CON Singapore 2026 TISC ESP32 Trinket note

challenge-artifact classification · official C517 source plus first-hand finalist writeup · documented

The ESP32 trinket is documented as a TISC finals challenge device handed to finalists, not as an all-attendee DEF CON Singapore badge or universal conference credential.

The catalogue includes it as a source-backed C517 Village challenge artifact while avoiding an official admission-badge claim.

Source note: CSIT C517 Village page, U-Zyn Chua finalist writeup, and DEF CON Singapore event page.

AND!XOR DC26 Badge note

challenge-completion caveat · primary retrospective · documented

The retrospective says more than four dozen people actively worked on the B.E.N.D.E.R. challenges, but that no individual player beat the full game during the event because progress was spread across different challenge areas and social collaboration did not converge in time.

The software record describes the intended and observed challenge surface without implying a completed public solve path for every attendee.

Source note: AND!XOR DC26 retrospective.

BSides Tampa 2026 Badge Challenge note

challenge-detail caveat · official source but intentionally narrow · needs post-event walkthrough

The badge-challenge page deliberately withholds hints and says it is possible there may not be a winner this year; this pass did not recover an official puzzle solution, final badge artwork, clue inventory, or challenge source archive.

The entry keeps the challenge description narrow until an official or first-hand walkthrough appears.

Source note: BSides Tampa 2026 badge-challenge page.

The Shattered Shard (DEF CON 34) note

challenge-details, participant-data, software-release, support, and license boundary · public Player Guide only · high-level player guide published; complete archive and terms unrecovered

The guide describes a badge-local quest, configurable participant handle, local network settings, saved progress, serial interaction, and reset/recovery concepts, but the reviewed repository exposes no implementation source, firmware/binary, board files, release/tag, license, build/deployment record, challenge-state/data-retention policy, privacy/security review, event terms, vulnerability policy, recovery package, support channel, warranty, or image-reuse grant. The guide itself directs use only of the assigned badge and advertised services.

The catalogue intentionally does not reproduce connection credentials, network or local-service details, flags, hidden resources, challenge hints, serial commands, reset steps, or exploit material; it also does not imply a privacy/security review, safe operational configuration, reproducible build, legal reuse, or ongoing support.

Source note: The Shattered Shard Player Guide and repository root, reviewed 2026-08-05.