BSides Bournemouth 2025 · United Kingdom · 2025

BSides Bournemouth 2025 Skull Badge

ATtiny402 skull PCB badge

A completed BSides Bournemouth 2025 electronic PCB badge created by the event's badge sponsor, Punk Security. BSides Bournemouth's official 2025 page establishes its Bournemouth 2600-led community cybersecurity conference and reports 200+ attendees; the Security BSides schedule records the August 16 date. Punk Security's own event page identifies it as badge sponsor and calls the artifact a Punk BSides skull badge, while its post-event repository identifies the Skull Badge and preserves EAGLE, Gerber, Arduino firmware, vector, and printed-art material. The archive names an ATtiny402, button, two CR2032 clips, and 5050 NeoPixel. The sources do not establish a production quantity, attendee allocation, individual handoff, final unit-by-unit configuration, safety validation, or reusable image provenance.

EventBSides Bournemouth 2025
SeriesBSides Bournemouth
LocationBournemouth, England, United Kingdom
CountryUnited Kingdom

People

Authors & Credits

2025 event organizer and official event publisher

BSides Bournemouth / Bournemouth 2600

BSides Bournemouth's official 2025 page identifies the event as organized by Bournemouth 2600 and establishes community conference context. This preserves event context only, not badge design, manufacture, distribution, image-rights, or source-archive ownership.

Source

source-named 2025 badge sponsor, maker, and repository publisher

Punk Security

Punk Security's event listing identifies it as the 2025 BSides Bournemouth badge sponsor, and its public repository identifies the Skull Badge and preserves source material. This credit reflects the publicly named sponsor/maker/archive roles without assigning attendee allocation, safety, event-organizer authority, or image rights.

Source

Why It Mattered

It fills an unseeded completed United Kingdom Security BSides artifact with official conference context, a dated maker/sponsor statement, and a public design-and-firmware archive. The record separates a real sponsor badge from unsupported assumptions that all 200+ reported attendees received the same unit or that a reference parts list maps exactly to every physical build.

Hardware

The public archive describes an ATtiny402 microcontroller, one surface-mount button, two CR2032 battery clips, and one 5050 NeoPixel addressable LED, and preserves EAGLE board/schematic, Gerber, vector, and silkscreen-art material. Its README says the stated parts match the BSides Cheltenham 2024 badge reference list. The sources do not establish final component substitutions, battery brand/capacity, power budget, protection behavior, runtime, electrical limits, production revision, assembly quality, or safety outcome for every physical unit.

Software & Apps

Punk Security's source archive preserves an Arduino firmware sketch for the Skull Badge. The record does not reproduce flashing, configuration, connection, modification, or hardware-assembly directions and does not claim a tagged release, signed binary, source-to-unit mapping, support policy, or all-unit firmware parity.

Lore

BSides Bournemouth describes its 2025 edition as a grassroots community cybersecurity conference organized by Bournemouth 2600, a local chapter of the global 2600 hacker community. Punk Security's dated event listing says it was the 2025 badge sponsor and invited people to collect its skull badges at its stand. The public archive calls the physical form the Skull Badge; sponsor evidence and reported attendance are not treated as a production or recipient ledger.

Source-backed hardware metadata

Technical Profile

Structured technical signals seeded from public badge documentation, repositories, schematics, firmware notes, or event evidence. These fields are designed for filtering, API use, repair planning, preservation, and future Companion Gear matching.

Artifact type

  • Electronic badge documented

    Punk Security's public repository identifies the Skull Badge as the BSides Bournemouth 2025 electronic badge. It does not establish attendee-wide allocation, final unit parity, or image rights.

    Signal source

Display / visual output

  • WS2812 / NeoPixel LEDs documented

    The repository's stated parts list names one 5050 NeoPixel addressable LED. The signal does not establish package substitutions, current budget, brightness, power behavior, or final-unit parity.

    Signal source

Power

  • CR2032 documented

    The repository's stated parts list names two CR2032 surface-mount battery clips. It does not establish battery brand, capacity, protection, power budget, runtime, electrical safety, or final-unit parity.

    Signal source

Firmware

  • Arduino documented

    The public firmware is an Arduino sketch using the MegaTinyCore interface for the ATtiny4x2 family. This records a source-bounded software lineage, not a supported or safe reconfiguration procedure.

    Signal source

Repair, preservation, and legal lab context

Companion Gear

Parts, tools, and supplies that match this badge's documented hardware, protocols, or preservation needs. These are category-level recommendations, not compatibility guarantees.

Amazon likely

Battery and Power Supplies

Battery holders, connectors, and safe replacement supplies for preservation work.

Why this matches

This badge has documented battery or rechargeable power hardware. Matched technical signals: CR2032.

Matched evidence

Handle lithium cells and replacement batteries only with appropriate safety practices.

Open vendor search

Vendor link · selected for technical relevance

Amazon generic

ESD Storage

Anti-static bags and storage supplies for preserving loose badge PCBs and sensitive components.

Why this matches

This is documented as an electronic or hardware artifact where anti-static storage can support preservation. Matched technical signals: Electronic badge.

Matched evidence

Useful for preserving loose PCBs, add-ons, and sensitive electronic components.

Open vendor search

Vendor link · selected for technical relevance

Lifecycle

Add-ons & Upgrades

event sponsor and maker relationship official sponsor listing and public source archive

Punk Security badge-sponsor event association

Punk Security's own event listing says it was BSides Bournemouth's 2025 badge sponsor and identifies Punk BSides skull badges, while its public repository identifies the Skull Badge for the event. This establishes a maker/sponsor event association without claiming the event organizer owned the archive or that every attendee received a unit.

Compatibility: BSides Bournemouth 2025 Skull Badge only; not a general Security BSides credential or admission entitlement

Source
manufacturing context maker-documented source archive

Full-colour printed PCB manufacturing context

The maker says the badge used full-colour printed PCB artwork and an EasyEDA preparation path. This records source-described manufacturing context without inferring a complete supplier record, production count, final materials, inspection plan, or quality outcome.

Compatibility: BSides Bournemouth 2025 Skull Badge source-design context only; no supplier, manufacturing, or safety endorsement

Source
physical badge design maker-documented source archive

Skull PCB form and printed-art context

The repository calls the artifact the Skull Badge and preserves vector and printed-board-art material alongside EAGLE and Gerber sources. This records the documented form without claiming every delivered unit used an identical final board, art revision, assembly quality, or manufacturing finish.

Compatibility: BSides Bournemouth 2025 Skull Badge source-design context; no generic hardware or art-reuse claim

Source
source-material archive maker-published after event

Public design and firmware archive

Punk Security's public repository preserves EAGLE, Gerber, Arduino firmware, vector, and printed-art material. The archive is linked for provenance without presenting it as a licensed derivative-work, manufacturing, flashing, or safety guide.

Compatibility: Punk Security source archive only; licence, final-release, and all-unit parity remain unresolved

Source

Operational history

Issues & Camp Impact

BOM provenance, final hardware, power, and electrical-safety gap note

The repository names an ATtiny402, button, two CR2032 clips, and 5050 NeoPixel but says its listed parts are the same as a BSides Cheltenham 2024 badge reference. The reviewed sources do not establish an exact final Bournemouth 2025 BOM, component substitutions, battery brand/capacity, polarity/protection behavior, power budget, runtime, electrical limits, thermal result, assembly quality, manufacturing test plan, certification, compliance, or safe service outcome.

The record preserves a source-backed hardware outline and its reference-list limitation without treating it as a complete fabrication, repair, electrical-safety, or universal final-unit specification.

Confidence
public repository review
Status
reference parts statement and design files public; production/safety result unrecovered
Timeframe
current catalogue build
Source note
punk-security/bsides-bournemouth-2025-badge README, EAGLE source, and Gerber archive.
badge-sponsor relationship, allocation, and handoff boundary note

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.

Confidence
official event context, Punk sponsor listing, and maker archive
Status
completed event and sponsor badge documented; recipient scope unrecovered
Timeframe
BSides Bournemouth 2025
Source note
BSides Bournemouth 2025 official page and Security BSides listing; Punk Security event listing; Skull Badge repository.
firmware release and operating-procedure boundary note

The source tree includes a firmware sketch and external development references, but reviewed sources do not establish a tagged final release, signed binary, source-to-unit mapping, build lockfile, deployment inventory, update policy, recovery process, support lifecycle, or safe end-user operating or reconfiguration procedure. No flashing, configuration, connection, or assembly directions are reproduced here.

The catalogue links source evidence without presenting it as a supported, reproducible, current, or safe modification workflow.

Confidence
public repository review
Status
firmware sketch published; final deployment/support record unrecovered
Timeframe
current catalogue build
Source note
bsides-bournemouth-2025-badge repository and firmware sketch.
missing rights-cleared image note

No BSides Bournemouth 2025 Skull 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 Kingdom record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.

Confidence
local project policy
Status
needs licensed original replacement
Timeframe
current catalogue build
Source note
badge.gallery image policy and BSides Bournemouth official 2025 page and Security BSides schedule plus Punk Security's badge-sponsor page and public Skull Badge repository.
source-license, visual-material, and branding scope boundary note

GitHub metadata reports a null detected license for the repository, and no root LICENSE or COPYING file was recovered in the public tree. The public repo contains board images, vector, and printed artwork, but neither it nor event/sponsor pages pair a selected factual badge photo or official render with an image-specific reuse basis, named attribution, source URL, and processing provenance.

Source files and public project material are cited as evidence, but no local image, artwork, source file, or brand asset is copied or treated as licensed for reuse.

Confidence
GitHub API metadata and repository-tree review
Status
no detected repository license; image rights unresolved
Timeframe
current catalogue build
Source note
GitHub repository metadata and file tree; BSides Bournemouth and Punk Security public pages; badge.gallery image policy.

Resources

Sources