BSides Peoria

BSides Peoria 2025

The completed October 25, 2025 Illinois Security BSides conference at Bradley University. The organizer's contemporaneous ticket announcement fixes the date and venue, while its 2026 retrospective says the prior event drew nearly 350 people and had electronic badges. Technet8394's public HackTheBadge archive calls itself code for the BSides Peoria Badge Challenge 2025, but the organizer does not directly link that source or establish a main-badge, attendee-allocation, or delivery relationship.

Bradley University, Peoria, Illinois · United States · 2025

BSides Peoria 2025 HackTheBadge Challenge Badge

A source-bounded independent BSides Peoria 2025 challenge-badge dossier. Technet8394's event-period public HackTheBadge README calls the work "My ESP32 code for the BSides Peoria Badge Challenge 2025." Its later source release documents an ESP32, a 240×320 ILI9341 TFT panel, two batteries, and wiring. BSides Peoria's official 2025 announcement establishes the October 25 Bradley University event, and its 2026 organizer retrospective says the prior edition drew nearly 350 people and had electronic badges. No reviewed organizer source links this specific maker project to a main attendee badge, official issuance, or completed handoff, so the catalogue keeps it as an independent event-associated challenge device.

Lifecycle

Add-ons & Upgrades

BSides Peoria 2025 HackTheBadge Challenge Badge event-period README; final device unverified

maker-published hardware outline

Maker-stated ESP32 and ILI9341 TFT parts surface

The pre-event README names an off-the-shelf ESP32, a 240×320 ILI9341 TFT panel, wiring, and two batteries. This establishes a maker-stated parts surface only; it does not prove a PCB, enclosure, wearable form, final board/module, battery chemistry/capacity/protection, power budget, or an event-unit configuration.

Compatibility: Technet8394's self-described BSides Peoria Badge Challenge 2025 project only; physical form and event-unit parity unverified

BSides Peoria 2025 HackTheBadge Challenge Badge source visible; event deployment unverified

post-event Arduino source context

Source-level Wi-Fi and display challenge surface

The post-event Arduino-style source contains Wi-Fi, local web-server, SPI, preferences, and ILI9341 display code. The catalogue records this high-level source context without publishing connection details, credentials, URLs, endpoints, challenge answers, access steps, or a claim that the visible code was deployed at the event.

Compatibility: Public HackTheBadge source archive; network configuration, device state, challenge parity, and operating conditions unverified

BSides Peoria 2025 HackTheBadge Challenge Badge repository existed before the event; code published after it

source chronology

Post-event public source-release trail

The repository's visible history has an event-period README before the October 25 conference, while the main Arduino source appears in a November 21 post-event commit. The chronology preserves public evidence without equating the later checkout with a dated event binary or documented final artifact.

Compatibility: HackTheBadge public repository only; no tagged event release or source-to-device mapping

Operational history

Issues & Camp Impact

missing rights-cleared image · local project policy · needs licensed original replacement

No BSides Peoria 2025 HackTheBadge Challenge Badge image is published because the current public source trail has not been paired with a reusable original badge or artifact photo or official upstream raster render with source URL, license or permission basis, attribution, and processing notes.

The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.

organizer-to-maker association, issuance, and allocation boundary · official organizer pages plus maker-published repository · event and electronic-badge context verified; direct project link unrecovered

BSides Peoria's official sources establish the completed October 2025 event and later state that its electronic badges were memorable, while Technet8394's repository self-identifies as a BSides Peoria Badge Challenge 2025 project. No reviewed organizer source links the repository, names this device, identifies its author, calls it an official main badge, or records a ticket tier, distribution count, recipient group, pickup, sale, giveaway, or completed handoff.

The catalogue models a real maker-declared event-associated challenge artifact rather than presenting it as organizer-issued, attendee-wide, admission-bearing, or independently confirmed electronic hardware.

physical form, component parity, power, and safety boundary · maker README and source-tree review · high-level parts list visible; physical artifact details unrecovered

The maker identifies an ESP32, a TFT panel, wiring, and two batteries, and the later source configures an ILI9341 display. The public archive does not provide a schematic, PCB, Gerbers, enclosure/CAD, exact ESP32 module, wiring diagram, final component substitutions, battery chemistry/capacity, charge/protection design, power budget, electrical limits, assembly/test record, production count, physical photo provenance, or safety validation.

The entry records a narrow source-backed electronic challenge-device outline without treating it as a reproducible build, a safe assembly guide, a uniform physical badge, or a completed production run.

source release, deployed-firmware, and interaction boundary · repository chronology and maker wording · post-event Arduino source visible; event deployment and support unrecovered

The archive's public main.ino source was added after the event, has no reviewed compiled binary, tag, GitHub release, explicit repository license, deployment record, support policy, or source-to-device mapping. Its maker describes the project as a one-off challenge. The code's Wi-Fi and web-server surfaces are therefore treated as source context rather than a live service, accessible challenge, secure workflow, or operating instruction.

The catalogue does not expose connection or challenge details, claim a current working service, offer configuration guidance, infer a released event firmware, or treat public source visibility as a broad license or support commitment.

Resources

Sources