DEF CON 34 · United States · 2026
Independent ATtiny1614 DEF CON 34 badge-challenge fuzzer SAO
NilbinSec's public DC34 Main Badge Fuzzer SAO repository documents a standalone SAO designed to exercise interfaces on the official DEF CON 34 Human badge using information published before the conference. Its README describes three initial modes: GPIO1/GPIO2 stimulation on the left SAO port, an open-drain CPU wake assertion on GPIO4 of the right port, and an I²C-address listening sweep. The repository provides a KiCad schematic, BOM CSV, PCB archive, C firmware, and compiled hex/ELF files. The README explicitly warns that Mode 1 may harm the main badge and says a convention reflash might follow. This is source-backed pre-event independent challenge hardware, not proof of a finished run, sale, giveaway, pickup, compatibility with a final main-badge revision, authorization to probe another badge, official DEF CON issuance or admission, a reusable-image grant, or an explicit software/hardware licence.
People
The public repository is published under the NilbinSec GitHub account and identifies itself as the DC34 Main Badge Fuzzer SAO project. This records a repository-publisher role only, not sole hardware/firmware/art authorship, manufacture, distribution, DEF CON organizer status, target authorization, or image-reuse authority.
SourceIt records a current BadgeLife tool that is intentionally adjacent to an official conference-badge challenge without collapsing the two artifacts into one record. The public source is unusually specific about both implementation and risk: it gives readers a traceable ATtiny/SAO implementation trail while preserving the maker's own warning, the evolving-target boundary, and the absence of distribution or organizer-authorization evidence.
The public BOM identifies an ATtiny1614-SSN, one SAO v1.69bis connector, two momentary switches, four LEDs, a 1×3 pin socket, four 470-ohm resistors, and 0805 capacitors. The C source maps four status LEDs (green, amber, red, blue), a left mode-select switch, a right attack/trigger switch, GPIO1/GPIO2, I²C SDA/SCL, and GPIO4 behavior. It says UPDI is on PA0 and the project uses a serialUPDI programmer. The repository root contains a KiCad schematic, BOM CSV, and PCB archive, but does not establish final board population, power rail/current budget, component substitutions, physical dimensions, SAO electrical tests, connector orientation, safe host insertion/removal, ESD protection, battery/USB behavior, certification, or a user safety guide.
The included C firmware targets ATtiny1614 with avr-gcc and avr-libc. Mode 1 cycles GPIO1/GPIO2 patterns, releases them to high impedance, samples responses, and passively listens for edges; Mode 2 asserts GPIO4 low as an open-drain wake signal while the trigger is held; Mode 3 is implemented as a passive software I²C listener. The README describes a 0x00–0x7F I²C range, while the current source uses 0x08–0x77 and skips 0x19 and 0x3C. The README gives a make/avrdude serialUPDI flashing outline and says later convention reflashes are possible, but no tagged release, supported final-firmware mapping, checksums, fuse map, recovery procedure, support policy, or explicit licence is published.
NilbinSec frames the artifact as a quick, potentially useful or completely useless way to fuzz parts of the DEF CON 34 main badge challenge from the initial public information. Its own source says it could be reflashed at the convention as more challenge information appears. That establishes a maker-described pre-event challenge-tool relationship only; it does not establish DEF CON authorization, a distribution plan, a sanctioned challenge method, a target-badge warranty, ownership or permission for every connected badge, or successful on-site use.
Lifecycle
The source maps a left multi-press mode selector, right Attack/Trigger switch, four color-coded status LEDs, optional 9600-baud UART debug output, and ATtiny1614 serialUPDI programming context. The README gives an avr-gcc/ATtiny device-pack/avrdude outline and says a later convention reflash may happen, but no supported end-user programmer, fuse configuration, tagged release, update package, recovery guide, or warranty is published.
SourceThe README says Mode 1 cycles GPIO1/GPIO2 on the left badge port. The current source drives four two-bit patterns, releases the lines, samples them, and then listens for edges. NilbinSec explicitly warns that this mode may harm a main badge depending on its GPIO configuration, so the source does not establish a safe, supported, or authorized use on any connected device.
SourceThe README describes Mode 2 as triggering the open-drain CPU wake-up interrupt on GPIO4 of the right SAO port. The source holds its configured GPIO line low while the Attack/Trigger switch is pressed, then releases it to high impedance. This documents the public implementation, not a safe/authorized use, final badge compatibility, or successful challenge result.
SourceThe README broadly says Mode 3 cycles 0x00–0x7F while listening as an I²C slave. The source instead documents passive bus observation over 0x08–0x77 and explicitly skips 0x19 and 0x3C. It says it does not drive SDA/SCL or ACK, but this is still not a guarantee of target compatibility, complete address coverage, bus safety, or authorized testing.
SourceOperational history
The catalogue preserves the warning so the artifact is not mistaken for a harmless universal add-on. Do not infer electrical safety, non-destructive behavior, authorization, warranty coverage, or suitability for an unfamiliar badge.
The record retains both source statements instead of presenting the README range as an exact implementation or claiming coverage, reliability, safety, or compatibility for a final target I²C bus.
The catalogue can link the implementation without presenting it as licensed open hardware/software, a stable release, a reproducible final build, a safe reflashing process, or an ongoing support commitment.
The dossier links an inspectable design trail without asserting that every source-derived board is electrically compatible, safely assembled, safe to attach, or suitable for unattended modification.
The catalogue keeps the target relationship searchable while classifying this as independent BadgeLife hardware rather than official conference hardware, an access credential, a universal attendee item, or evidence of organizer endorsement.
The record remains source-backed and image-free rather than copying repository previews, GitHub user-attachment images, screenshots, social-media media, placeholders, or generated approximations.
The catalogue records a real public project without portraying it as a completed physical distribution, a universally available SAO, a confirmed sale/giveaway, or a completed DEF CON handoff.
Readers should not treat the public source as a compatibility guarantee, a target-specific exploit claim, an endorsement to connect the SAO, or authorization to interact with another attendee's hardware.