DEF CON 34 · United States · 2026
Pre-event independent two-object ESP32-S3 interaction badge project for DEF CON 34
Two contemporaneous project posts authored by the public Reddit account u/zer0patient and signed H4irl1n3 M0gg3r5 describe an independent planned DEF CON 34 Zombie Badge project. The later source explicitly describes two objects using ESP32-S3, IR, NFC, BLE, a buzzer, and a source-described transmission/counter relationship; it also announces a firmware-based, multi-stage CTF and an unreleased backend. It further describes crew-operated live transmission zones, fixed Cure Stations, hidden 3D-printed medkit props, and a separate brain-in-a-jar SAO. The earlier post calls the work the team's first year making badge or badges, says a second variant is part of the experience, and announces intended drop-based distribution. These are source-backed pre-event maker statements about a real planned artifact system, not proof of final manufactured variants, component selection, wireless behavior, game implementation, inventory, drops, event authorization, DEF CON organizer affiliation, conference admission, or reusable-image rights.
People
The early and detailed public Reddit updates are authored by u/zer0patient. This is a narrow public-post attribution and does not identify the person's legal identity, employer, role within H4irl1n3 M0gg3r5, engineering authorship, or image-reuse authority.
SourceThe detailed project announcement is signed H4irl1n3 M0gg3r5. This records the source-named team/project role without inferring individual hardware authorship, manufacturing responsibility, DEF CON organizational status, or image-reuse authority.
SourceThis entry captures a rare current DEF CON 34 badge project that documents a deliberately paired, in-person interaction concept instead of merely showing a board photo. It preserves the high-level technical and game claims that the project team actually published, while holding a firm line between an announced scenario and a shipped, testable system: role-play wording is not a protocol specification, an announced CTF is not a released challenge archive, and a Reddit image is not cleared for republication.
The H4irl1n3 M0gg3r5 announcement calls the project two objects and names ESP32-S3, IR, NFC, BLE, a buzzer, and a silkscreen whose meaning is part of the game. It says one object transmits and another was built to counter it. The same source separately announces a brain-in-a-jar SAO that can affect transmission objects in range. It does not identify the exact ESP32-S3 module, board or antenna design, IR/NFC/BLE implementation, frequencies, power source, battery/charger, connectors or SAO pinout, sensor model, buzzer part, dimensions, materials, schematic, BOM, PCB/Gerbers, firmware image, final revision, test data, safety guidance, compliance evidence, or compatibility matrix.
The team says the CTF lives in firmware, is multi-stage and not solo-completable, uses real protocols, and has backend pages that require progress to reach. It does not publish a firmware binary or source tree, challenge archive, protocol description, build or flashing instructions, backend URL or API, score-validation policy, player-data policy, authentication model, update or recovery path, software license, dependency inventory, final game rules, or proof that the announced experience will run as described.
The early project post frames the artifact around the words Touch, Infect, Transmit, and Survive, says a second variant is necessary to progress, and announces drops designed to make receiving one part of the experience. The later team-signed announcement places the planned game at DEF CON 34 in Las Vegas: crew members are described as roaming live transmission zones, Cure Stations as fixed but unmapped, and medkits as hidden 3D-printed props. These establish a planned independent BadgeLife-style game setting, not an official DEF CON activity, guaranteed drop, venue authorization, prize, organizer endorsement, or access credential.
Lifecycle
The early project post says the maker intends to do drops and make receiving a badge part of the experience; it also says a second variant is necessary for the interaction. It does not publish quantities, price, sales channel, dates, selection method, pickup or shipping terms, allocation, recipient list, completed drop, or final count of variants.
SourceThe team says the CTF lives in firmware, is multi-stage and not solo-completable, uses real protocols, and unlocks backend pages through progress. No code, binary, challenge archive, protocol specification, endpoint, scoring system, access policy, data policy, or final running service is published in the reviewed sources.
SourceThe team says the project consists of two objects with ESP32-S3, IR, NFC, BLE, and a buzzer; one transmits while another was built to counter it. The source does not identify exact modules, electrical design, radio configuration, protocol, range, antenna, power system, test method, final revision, or delivered behavior.
SourceThe team describes crew members as roaming live transmission zones, fixed but unmapped Cure Stations, and hidden 3D-printed medkit props. This is a planned game surface, not proof of venue approval, final locations, staff participation, accessibility, safety review, implementation, participant effect, prize, or event outcome.
SourceThe team announces a brain-in-a-jar SAO and says tapping it causes something to happen to transmission objects in range. The source does not publish connector/pinout, electrical requirements, host compatibility, radio or proximity mechanism, availability, final behavior, safety guidance, or technical archive.
SourceOperational history
The record does not convert a game announcement into a reproducible software release, operational service, security claim, data-handling guarantee, or solution guide.
The dossier preserves the published technical nouns without treating them as a complete electrical design, interoperable standard, safe-use instruction, or confirmed production specification.
Readers can see the intended collaborative game context without assuming that proximity effects, wireless behavior, data use, safety, or onsite logistics were implemented, authorized, or suitable for every participant.
The catalogue classifies the Zombie Badge as an independent pre-event project associated with DEF CON 34, not an official conference credential, organizer-issued badge, admission item, or verified event activity.
The record remains source-backed and image-free rather than copying Reddit photos, previews, screenshots, social-media media, placeholders, or generated approximations.
The catalogue records a real planned artifact system without representing it as manufactured, acquired, delivered, stocked, or experienced by a confirmed attendee population.