Repository navigation
Hardware Hacking
Physical and electronic attack techniques against embedded systems, microcontrollers, SoCs, and cryptographic hardware
Part of the ULTIMATE CYBERSECURITY MASTER GUIDE
Adjacent embedded-security research: Awesome Embedded and IoT, h4cker hardware and project routing.
| Resource | Description / Boundary |
|---|---|
| Device Firmware List | Board-first choices and target limitations. |
| The Black Wire Maker's Technical Reference Guide | Board pinouts, GPIO diagrams, wiring references and manufacturer documentation for Raspberry Pi, ESP32, Arduino and related embedded boards. |
| ESP Terminator | General catalog/uploader selection and recovery checks. |
| Resource | Role & Compatibility Boundary |
|---|---|
| ESP32 Bit Pirate | S3 firmware install and a read-only UART bench baseline; distinct from Bus Pirate hardware. |
| Pico-Ducky Lab | Pico setup mode and a fixed-text offline HID demonstration. |
| Flipper Expansion Board Labs | CC1101, nRF24/Si24R1, AWOK Dual C5, Realtek BW16, Poltergeist, RF-safe wiring & eight validation labs. |
| Evil-M5 Field Labs | Cardputer/ADV and other M5Stack target setup, eight safe RF/BLE/HID and defensive lab exercises. |
| LAB5 MonsterC5 / JanOS | Distinct C5 radio, Cardputer/Tab5/Flipper apps, verified update path and eight tests. |
| Resource | Description |
|---|---|
| ESP32 & Related Firmware Catalog | Primary upstream projects, supported targets, use-cases & dated activity notes |
| Firmware Web Flashers | Dedicated installers plus a separate multi-device/multi-firmware reference |
Index and navigation hub for the Hardware Hacking section - covering physical and electronic attack techniques against embedded systems: JTAG/SWD/UART debug access, fault injection (voltage, clock, EM, laser), side-channel analysis (SPA, DPA, CPA), firmware extraction, and the hardware tools used in each category.
Links to five chapter guides (threat modeling, electrical fundamentals, fault injection, power analysis theory, power analysis practicals) and seven device guides (Bus Pirate, Bit Pirate, GreatFET One, JTAGulator, LA1010 logic analyzer, HiLetgo logic analyzer, T48 IC programmer). Includes attack category taxonomy, bench equipment reference, and tool ecosystem overview.
Serve as the entry point for hardware security work - helping practitioners find the right chapter or tool guide for their current task without reading the full guide linearly.
- Starting a hardware security assessment: choose the right chapter and tool for your target
- Identifying which hardware tool to use for a given protocol or attack type
- Onboarding to hardware hacking: read chapters in order, then reference tool files for specific devices
- Overview
- Hardware Security Case Studies
- Chapter Guides
- Device Setup & Usage Guides
- Attack Categories
- Bench Equipment Reference
- Tool Ecosystem
- Security & Legal Disclaimer
- Resources
Hardware security assessment includes physical access, debug interfaces, firmware, power traces, timing, and electromagnetic emissions. Physical access may create opportunities that are unavailable through a remote network path, but actual risk depends on the target design, exposed interfaces, attacker resources, and existing controls.
This section organizes study from threat modeling and electrical fundamentals through fault injection and side-channel analysis. Use the chapter and device-specific guides for detailed material, and check it against the exact target and documentation.
Conceptual overview: define scope and safety limits first, establish a non-destructive baseline, choose a method for the question, separate observation from inference, then report and restore under the owner's direction.
What You'll Find Here:
- ๐ฏ Hardware threat modeling: Attacker profiles, asset mapping, countermeasure frameworks
- โก Electrical fundamentals: Logic levels, communication interfaces (UART, SPI, IยฒC, JTAG/SWD), measurement equipment
- ๐ฅ Fault injection attacks: Voltage glitching, clock glitching, EMFI, laser fault injection, body biasing
- ๐ Side-channel analysis: Timing attacks, Simple Power Analysis (SPA), Differential Power Analysis (DPA)
- ๐ฌ Power analysis practicals: Measurement setup, trace acquisition, filtering, CPA implementation, visualization
- ๐ก๏ธ Countermeasures: Silicon-level, firmware-level, and physical protections
- ๐ Device-specific guides: Setup, connection, and usage tutorials for common hardware hacking tools.
The Case Studies Index gives sourced reports with research timelines, practical limitations and defensive responses. Use it alongside the bench guides; a disclosed flaw must not be treated as proof that the particular equipment in front of you is affected.
| Case Study | Relevant Hardware Boundary | Complementary Guide |
|---|---|---|
| Unsaflok โ Three Million Hotel Locks | RFID credential trust & room authorization | RFID/NFC |
| Onity Locks, 2012 | Accessible service ports & firmware authorization | Electrical Interfaces |
| Tesla Model S Key Fobs, 2018 | RF protocol and key lifecycle | SDR & RF |
| EUCLEAK / YubiKey, 2024 | EM side-channel cryptographic leakage | Timing & Power Analysis |
| DirecTV DSS Cards & Black Sunday | Smart-card authorization & countermeasure recovery | Threat Modeling |
| Xerox DocuColor Tracking Dots | Hidden physical-output metadata & privacy | OPSEC |
| Chapter | Topic | Description |
|---|---|---|
| Chapter1.md | Threat Modeling | Attacker profiles, asset categories, objective-to-attack mapping, countermeasure frameworks (silicon/firmware/physical), threat model template |
| Chapter2.md | Electrical Fundamentals | Ohm's Law, logic levels, communication interfaces (UART, SPI, IยฒC, JTAG, SWD), oscilloscopes, logic analyzers, shunt resistors, signal integrity |
| Chapter3.md | Fault Injection Attacks | Voltage glitching, clock glitching, EMFI, laser fault injection, body biasing, injection point identification, parameter sweeping, fault mapping |
| Chapter4.md | Timing & Power Analysis | Side-channel concepts, timing attacks (string comparison, RSA, cache), Simple Power Analysis (SPA), Differential Power Analysis (DPA) with working code |
| Chapter5.md | Power Analysis Practicals | Measurement setup, trace acquisition, filtering (low-pass, band-pass), trace alignment (SAD, cross-correlation), CPA implementation, visualization, TVLA, template attacks |
New to hardware hacking?
โโ> Start with Chapter 1 (Threat Modeling) for framework and terminology
โโ> Then Chapter 2 (Electrical Fundamentals) for bench skills
โโ> Then Chapter 3 (Fault Injection): most accessible attack category
โโ> Then Chapters 4โ5 (Side-Channel): builds on measurement fundamentals
Experienced practitioner?
โโ> Jump directly to the relevant chapter
โโ> Chapter 3 for glitching campaign setup
โโ> Chapter 5 for CPA implementation and visualization code
โโ> Chapter 1 for threat model documentation template
The existing Bash Bunny payload guide, USB Rubber Ducky compilation guide, and WiFi Pineapple Mark VII section now include authorized deployment labs, detection, troubleshooting and reporting. They remain in their established sections to avoid duplicating instructions. Pico-Ducky is distinct from Hak5 hardware.
Device formats are not interchangeable. The WiFi Pineapple Pager uses payload.sh and Pager-specific UI/events. The Mark VII uses Campaigns and Modules. Bash Bunny and Rubber Ducky have different USB runtimes. Other Hak5 devices have separate official payload repositories and firmware; a matching command name is not sufficient for compatibility.
| Platform | Official source / format | Safe first-use and sideload boundary |
|---|---|---|
| WiFi Pineapple Pager |
Official User/Recon/Alert payload library; on-device payload.sh
|
Copy a single reviewed local script to the correct Pager payload type, start with a no-radio message; do not use Mark VII campaigns |
| WiFi Pineapple Mark VII | Campaigns / Modules | Prefer built-in monitor-only campaign; validate module code, API version, package and UI support before third-party installs |
| Bash Bunny / Mark II |
Hak5 Bash Bunny payload library; Bash payload.txt with ATTACKMODE, QUACK
|
Review full source/dependencies, copy a benign HID marker into a single staged switch; match device generation and firmware |
| USB Rubber Ducky (modern/legacy) |
Official source library; source payload.txt compiled to inject.bin
|
Compile for the actual hardware/DuckyScript version and keyboard layout; verify a marker in a blank editor |
| Shark Jack | Official Shark Jack library; model-specific Bash/DuckyScript source | Use a spare isolated Ethernet test bench, not a client's switch; review DHCP, routing and any scan/transmit behavior |
| Shark Jack Display |
Official Display library; payload.txt
|
Distinct display/menu and payload flow; check exact product revision and NETMODE handling before copying sources |
| Packet Squirrel |
Official Packet Squirrel library; payload.txt
|
Inline Ethernet changes the traffic path; test with dedicated two-port lab link and rollback, not real production traffic |
| Key Croc |
Official Key Croc library; payload.txt
|
In-line keyboard hardware can capture sensitive input; baseline test only with a synthetic user and approved marker |
| LAN Turtle | Hak5 LAN Turtle documentation and firmware modules (check exact model) | Separate USB-Ethernet remote administration tooling; no assumption that Shark Jack payload scripts run here |
| Signal Owl / Screen Crab / Plunder Bug | Hak5 documentation index | Separate hardware and capture/runtime requirements. Not every Hak5 device has a community payload.txt library |
Popular GitHub collections (curated, not automatically runnable): Rubber Ducky projects ranked by relevance, stars & compatibility and Bash Bunny payload collections & maintenance review. The guides identify original/archived repositories, distinguish Flipper/O.MG/Arduino references from Hak5 firmware, and explain pinning, code inspection, benign lab acceptance and rollback.
Important: the upstream sample collections may include interception, credential harvesting, command-and-control, persistence or disruptive network activity. Do not bulk-install, automatically run or endorse all samples. Prefer a fixed-text HID marker, an owned test AP inventory, or an isolated dummy Ethernet link, and only approve more intrusive testing under a separate signed plan.
- Select exact platform/firmware and model. Record payload interpreter, USB/network modes, switch position and the official source repository or versioned download.
- Pin a commit/hash, inspect the source (including bundled shell/PowerShell/Python executables and compressed archives), and verify license, external connections, credentials, dependencies, package installation, persistence, scheduled tasks and elevated operations.
- Decide authorization class: local benign, receive-only survey, active association/network traffic, credential/packet interception, persistent modification. Only benign exercises are default-approved.
- Isolate on a known-good bench: offline disposable workstation with blank editor for HID; lab AP/phone for Wi-Fi; two-device synthetic VLAN/link for network appliances. Snapshot or document rollback before execution.
- Stage one payload using the device's verified deployment directory. Do not assume a common root directory or file extension across Hak5 models. On USB devices, safely eject in arming/storage mode; avoid flashing the payload onto firmware partitions.
- Observe once: record USB enumeration, network/routes, emitted RF, local output, log timestamps, and intended versus actual destination. Stop on unexpected transmission, third-party interaction or changes to default route/DNS.
- Corroborate: use host endpoint events/EDR, AP-controller records, Kismet/Wazuh, test switch logs or known USB interface properties. A script exiting zero does not prove any vulnerability.
- Rollback, inventory and redact: stop payloads, disconnect, restore firmware/network configuration, rotate synthetic credentials, hash and securely store allowed artifacts, remove unnecessary copies from the device.
| Device | Controlled exercise | Expected evidence |
|---|---|---|
| Shark Jack / Shark Jack Display | Connect only to your lab switch and validate port link, DHCP address and local interface status without scanning other addresses | Port VLAN/link state, assigned lab IP, switch/host logs and restore |
| Packet Squirrel | Place between two owned lab Ethernet endpoints; verify links work in pass-through mode and observe what a deliberate disconnect does | End-to-end link checks, physical link indicators, clean bypass/rollback |
| Key Croc | Connect a disposable keyboard and test computer with a synthetic local-only username/marker; keep capture/matches disabled unless essential and approved | Host recognized keyboard, synthetic text, source review and no retained secrets |
| Bunny / Ducky | Type a fixed harmless phrase into a focused blank editor with no terminal or browser open | USB class enumeration, marker, no privilege changes or network transfer |
| Mark VII / Pager | Observe a single owned synthetic AP, then independently verify WIDS controller alert behavior without active impersonation | Correct BSSID/channel/security, actual source events and sanitized result |
| Symptom | Investigate |
|---|---|
| Payload ignored | Wrong hardware format, firmware interpreter, file path/case, permissions or wrong switch/category |
| Payload appears but errors | Missing device helper functions, incompatible DuckyScript generation, OS/tool dependency or bad CRLF endings |
| OS sees new keyboard unexpectedly | Wrong USB class / ATTACKMODE selected; disconnect and restore known-good switch |
| LAN traffic changes |
NETMODE/routing/bridge behaviour and link negotiation; stop inline device and restore direct cable |
| Unexpected AP or upload | Disable PineAP/alert or event action, disconnect management uplink and audit all scripts |
| Data not saved | Incorrect storage partition, missing media, no completed flush or script path assumption |
| Firmware update breaks payload | Firmware/API changed, packages removed, library helpers changed; restore pinned compatible version |
Primary sources: Hak5 official payload repositories ยท Pager source ยท Shark Jack ยท Packet Squirrel ยท Key Croc. Do not confuse a source repository's approved pull request with a complete firmware or security certification.
M5StickC Plus2: HackStarterPack integration and safe lab covers the exact board, CC1101 pinout, benign IR/BLE/HID tests and source review.
For ESP32/Flipper radio accessories used specifically for authorized mapping, see the Wardriving platform index, Scout Lite + SigRoam, Marauder, and AWOK Dual C5 + Biscuit. These cover board revisions, firmware roles and GPS/log locations.
Detailed documentation, reference links, and step-by-step usage tutorials for specific hardware hacking tools on your bench:
| Device Guide | Description |
|---|---|
| BusPirate.md | Open-source hacker multi-tool for interfacing with I2C, SPI, UART, and JTAG. |
| GreatFETone.md | Extensible open-source hardware tool for logic analysis, I2C/SPI manipulation, and USB RE. |
| JTAGulator.md | Tool for systematic pinout discovery on authorized hardware; possible results depend on target design and enabled interfaces. |
| BitPirate.md | Serial interface bridge for embedded systems recon, fuzzing, and debugging. |
| LA1010.md | Setup and usage for the Innomaker LA1010 100MHz 16-channel USB Logic Analyzer. |
| HiLetgo.md | Setup and usage for the HiLetgo 24MHz 8-channel USB Logic Analyzer (Saleae clone). |
| T48_TL866-3G.md | Programmer guide; supported parts, packages, voltages, and adapters depend on the exact manufacturer device-list entry. |
Introduce controlled transient errors to bypass security checks, skip instructions, or corrupt comparisons.
| Method | Equipment | Precision | Complexity | Cost |
|---|---|---|---|---|
| Voltage Glitching | MOSFET + FPGA or ChipWhisperer | Medium | Low | $ |
| Clock Glitching | FPGA or ChipWhisperer | High | Medium | $$ |
| EMFI | ChipSHOUTER or custom coil + pulser | Medium-High | Medium |
|
| Laser FI | IR laser + XY stage + decapped chip | Very High | High | $$$$ |
| Body Biasing | Probe + pulse generator | Medium | Medium | $$ |
Side-channel methods study physical or timing observations correlated with device behavior. Trace requirements are target- and test-dependent; the values below are not universal.
| Method | Typical observation | What affects the evidence |
|---|---|---|
| SPA | Power or EM patterns in one or more operations | Algorithm, implementation, signal quality, and whether data-dependent steps are visible |
| DPA / CPA | Statistical relationship between a leakage hypothesis and repeated measurements | Leakage model, alignment, noise, input variation, and target implementation |
| Timing | Runtime differences across controlled operations | Input design, system noise, implementation, and measurement setup |
| SEMA / DEMA | Single-trace or differential electromagnetic observations | Probe position, coupling, bandwidth, signal quality, and target implementation |
| Template | Classification using a profiling set and attack observations | Quality and representativeness of profiling data, feature selection, and target similarity |
| TVLA | Statistical evidence of data-dependent leakage | Test design, sample quality, group selection, and statistical analysis; a non-detection does not prove resistance |
For ChipWhisperer examples, see the capture API and analyzer API. Neither defines a universal number of traces required for a successful assessment.
| Interface | Wires | Attack Value | Common Tools |
|---|---|---|---|
| UART | TX, RX, GND | Boot logs or console if exposed; a shell depends on target configuration | USB-UART adapter, logic analyzer |
| JTAG | TCK, TMS, TDI, TDO, TRST | Debug access where the interface is exposed, enabled, and authorized | J-Link, OpenOCD, JTAGulator |
| SWD | SWDCLK, SWDIO | ARM two-wire debug; distinct from JTAG and subject to target access controls | ST-LINK, CMSIS-DAP |
| SPI | SCLK, MOSI, MISO, CS | Read/write access only when a supported memory device is connected and accessible | flashrom, Bus Pirate, CH341A |
| IยฒC | SDA, SCL | EEPROM read/write, PMIC manipulation | i2ctools, Bus Pirate |
Budget figures below are rough estimates, not current quotes. Prices vary by region and seller; confirm current pricing, included adapters, and exact target compatibility before purchase.
| Equipment | Recommended | Budget | Purpose |
|---|---|---|---|
| Oscilloscope | Rigol DS1054Z / Siglent SDS1204X-E | $350โ$400 | Signal capture, power analysis, glitch verification |
| Logic Analyzer | Innomaker LA1010 / HiLetgo / DSLogic | $10โ$150 | Protocol decode (UART, SPI, IยฒC, JTAG) |
| Multimeter | Any decent DMM | $20โ$50 | Voltage/continuity checks |
| USB-UART Adapter | FTDI FT232R / CP2102 | $5โ$15 | Serial console access |
| JTAG/SWD Probe | J-Link EDU / ST-LINK V2 | $20โ$70 | Debug interface access |
| SPI/IC Programmer | T48 TL866-3G / Bus Pirate | $35โ$70 | Read/write supported parts only; verify the exact chip and required adapter |
| Soldering Station | Hakko FX-888D | $100 | Component removal, wire attachment |
| Hot Air Rework | Quick 957DW or equivalent | $100โ$200 | IC removal, BGA work |
| Equipment | Recommended | Budget | Purpose |
|---|---|---|---|
| ChipWhisperer Lite | NewAE Technology | ~$250 | Integrated glitching + power analysis |
| ChipWhisperer Pro | NewAE Technology | ~$1,500 | Higher performance, more glitch options |
| ChipSHOUTER | NewAE Technology | ~$1,000 | Electromagnetic fault injection |
| JTAGulator | Grand Idea Studio (Guide) | ~$150 | JTAG/UART pinout brute-force |
| Glasgow Interface Explorer | Open-source FPGA | ~$150 | Scriptable multi-protocol interface |
| GreatFET One | Great Scott Gadgets (Guide) | ~$100 | Multi-purpose interface and bus manipulation |
| Tool | Purpose | Cost | Reference Guide |
|---|---|---|---|
| ChipWhisperer | Integrated glitching + power analysis platform | $250โ$1,500 | N/A |
| ChipSHOUTER | EMFI pulse injector | ~$1,000 | N/A |
| JTAGulator | JTAG/UART pinout discovery | ~$150 | JTAGulator.md |
| Glasgow | FPGA-based scriptable interface explorer | ~$150 | N/A |
| Bus Pirate | Interactive multi-protocol interface tool | ~$35 | BusPirate.md |
| GreatFET One | USB/Logic/Interface exploration | ~$100 | GreatFETone.md |
| T48 TL866-3G support list | Programmer for listed ICs; verify package, voltage, and adapter | ~$65 | T48_TL866-3G.md |
| LA1010 / HiLetgo | USB Logic Analyzers (100MHz / 24MHz) | $15โ$50 | LA1010.md & HiLetgo.md |
| Tool | Purpose | Cost |
|---|---|---|
| OpenOCD | Open-source JTAG/SWD debug | Free/OSS |
| flashrom | SPI/parallel flash read/write | Free/OSS |
| Ghidra | Firmware reverse engineering; local guide and upstream project | Free/OSS |
| IDA Pro | Firmware reverse engineering | $$$$ |
| Binwalk | Firmware extraction and analysis | Free/OSS |
| Sigrok / PulseView | Open-source logic analyzer frontend | Free/OSS |
| ChipWhisperer Software | Jupyter-based SCA/FI tutorials | Free/OSS |
| Library | Purpose | URL |
|---|---|---|
| scared | Side-channel analysis framework | Free/OSS |
| lascar | Flexible SCA framework (Ledger) | Free/OSS |
| SCARR | Side-channel analysis framework (Oregon State) | Free/OSS |
| NumPy / SciPy / Matplotlib | Trace processing, filtering, visualization | Free/OSS |
โ ๏ธ LEGAL AND ETHICAL USE ONLY โ ๏ธ
This section contains hardware attack techniques and methodologies for:
โ
AUTHORIZED USES:
โข Security assessments with explicit written authorization from device owners
โข Red team operations with organizational approval
โข Academic research on owned or authorized hardware
โข Product security evaluation by manufacturers
โข CTF competitions and authorized challenges
โข Personal research on your own hardware
โข Educational purposes with proper supervision
๐ซ STRICTLY PROHIBITED:
โข Attacking hardware you do not own or have authorization to test
โข Bypassing DRM or copy protection in violation of DMCA
โข Extracting proprietary firmware or trade secrets without authorization
โข Cloning, counterfeiting, or pirating commercial products
โข Tampering with safety-critical systems (medical, automotive, aviation)
โข Any activity violating CFAA, DMCA, or equivalent laws
โข Any illegal or unethical activities
| Law / Regulation | Scope |
|---|---|
| CFAA (18 U.S.C. ยง 1030) | Unauthorized access to protected computers: includes embedded systems |
| DMCA (17 U.S.C. ยง 1201) | Circumvention of technological protection measures (DRM bypass) |
| EAR / ITAR | Export controls on certain cryptographic and defense-related hardware tools |
| Trade Secret Laws | Extraction of proprietary firmware or algorithms may constitute misappropriation |
| EU Cybercrime Directives | Unauthorized access to computer systems including embedded devices |
| DMCA ยง 1201(j) | Security research exemption: narrow; consult legal counsel |
These materials are provided "AS IS" without warranty of any kind.
THE AUTHORS AND CONTRIBUTORS:
โข Make no guarantees about technique effectiveness or accuracy
โข Are not responsible for damage to hardware during testing
โข Are not liable for legal consequences of misuse
โข Disclaim all liability for injury from high-voltage equipment
โข May update content without notice
USERS EXPLICITLY ACKNOWLEDGE:
โข Hardware hacking involves electrical hazards (high voltage, laser, EM pulses)
โข Fault injection can permanently damage target devices
โข They accept all risks including equipment damage and personal injury
โข Authorization must be explicit and from the device owner
๐ด ELECTRICAL SAFETY:
Hardware hacking involves potentially dangerous equipment:
โข High-voltage pulse generators (EMFI, LFI)
โข Laser sources (Class 3B/4: eye damage risk)
โข Soldering and hot air rework (burn risk)
โข Chemical decapping agents (fuming acids: fume hood required)
ALWAYS:
โ Wear appropriate PPE (safety glasses, gloves, lab coat)
โ Work in a ventilated area for chemical decapping
โ Use laser safety goggles rated for the correct wavelength
โ Follow your institution's EHS guidelines
โ Never work alone with high-voltage equipment
To contribute to the Hardware Hacking section:
- Fork the repository
- Follow the 4-header standard:
## ๐ฏ Purpose,## โ๏ธ Function,## ๐ Goal,## ๐ When to Useafter every H1 - Include written authorization reminders for any offensive technique
- Add electrical and physical safety warnings for hands-on procedures
- Note the exact tool model, firmware version, and OS environment tested
- Submit a pull request with a description of the contribution
| Title | Author(s) | Focus |
|---|---|---|
| The Hardware Hacker | Andrew "bunnie" Huang | Hardware hacking philosophy and techniques |
| Hardware Security: A Hands-on Learning Approach | Bhunia, Tehranipoor | Academic hardware security |
| Power Analysis Attacks | Mangard, Oswald, Popp | DPA/SPA theory and practice |
| Fault Analysis in Cryptography | Joye, Tunstall (eds.) | Fault injection theory |
| Resource | URL |
|---|---|
| ChipWhisperer Documentation & Tutorials | https://chipwhisperer.readthedocs.io/ |
| Microcorruption CTF (MSP430 exploitation) | https://microcorruption.com/ |
| CHES Conference Proceedings | https://ches.iacr.org/ |
| Riscure / Keysight Device Security Tools | https://www.riscure.com/security-tools/ |
| DEF CON Hardware Hacking Village | https://dchhv.org/ |
| Wrong Baud (hardware RE blog) | https://wrongbaud.github.io/ |
| Conference | Focus |
|---|---|
| CHES | Cryptographic Hardware and Embedded Systems: leading SCA/FI venue |
| DEF CON HHV | Hardware Hacking Village: hands-on workshops and talks |
| Hardwear.io | Dedicated hardware security conference |
| REcon | Reverse engineering: significant hardware content |
| USENIX Security | Academic security: regular hardware security papers |
- ๐ Main Repository
- ๐ฏ START HERE Guide
- ๐ป Cybersecurity Master Guide
- โ Security Checklists
- ๐ฐ๏ธ Space Security
- ๐ OSINT Resources
- ๐ Documentation
- ๐ OPSEC Guidelines
๐ Chapters: 5
๐ Covers: Threat modeling, electrical fundamentals, fault injection, side-channel analysis, power analysis
๐ Last Updated: June 2026
๐ฅ Maintained by: Pacific Northwest Computers (PNWC)
๐ Status: Active & Growing
- ../Documentation/Locksport.md - Physical lock bypass: complements hardware debug access in full red-team physical assessments
- ../Documentation/bruce_firmware.md - Bruce firmware: NFC/RFID and sub-GHz attacks on the wireless protocols used by embedded targets
- ../Documentation/flipper_zero_guide.md - Flipper Zero: RFID/NFC/sub-GHz tool for the RF-adjacent attack surface of embedded devices
- ../SDR/ - SDR guides: RF analysis of wireless-enabled embedded targets
- ../IncidentResponse/ - Incident response: detecting hardware-level attacks and evidence collection from embedded devices
- ../Cryptography/phantomdrive-guide.md - experimental CH569W hidden encrypted USB firmware research; not audited for client data
- ../Cryptography/solokeys-guide.md - Solo 2 Secure/Hacker firmware-security boundary and authentication use
- ../Mobile/README.md - Mobile security section (HID/BadUSB via NetHunter is a mobile hardware attack vector)
- ../CAD/README.md - CAD & 3D printing: design printed probe holders, test fixtures, PCB carriers and device enclosures; mock up boards and connectors before printing
- ../Mobile/mobile_pentest_sop.md - Mobile pentest SOP (HID and BadUSB attack procedures)
๐ Use These Techniques Responsibly: Authorization is MANDATORY
Physical access changes everything: test only what you own or are authorized to assess.
Repository: ULTIMATE CYBERSECURITY MASTER GUIDE
Maintained by: Pacific Northwest Computers
โญ Star this repo if you find it useful! โญ
- ๐ดโโ ๏ธ Bit Pirate
- ๐ดโโ ๏ธ Bus Pirate
- Chapter 1: Threat Modeling for Hardware Security
- Chapter 2: Electrical Fundamentals
- Chapter 3: Fault Injection Attacks
- Chapter 4: Timing and Power Analysis Attacks
- Chapter 5: Power Analysis - Practical Techniques
- ESP32 Bit Pirate: Protocol Bench Setup
- ๐ฆก GreatFET One (with Add-On Boards)
- ๐ HiLetgo USB Logic Analyzer (Model-Dependent)
- ๐ InnoMaker LA1010 USB Logic Analyzer
- ๐ท๏ธ JTAGulator
- M5StickC Plus2 โ HackStarterPack lab integration
- Pico-Ducky: Safe USB HID Setup & Validation
- ๐พ T48 TL866-3G Universal IC Programmer
๐ Folder: HardwareHacking | โ๏ธ Suggest an edit | ๐บ๏ธ Browse by Topic
- ๐บ๏ธ Browse by Topic
- ๐ All Repository Files
- ๐งญ Learning Paths
- ๐ Master Guide
- ๐ค Glossary
- โ๏ธ Legal & Disclaimer
๐ Foundations & Learning
๐ก๏ธ Defense & Investigations
- Incident Response
- Open Source Intelligence (OSINT)
- Reverse Engineering
- Operations Security (OPSEC)
- Compliance
โ๏ธ Platforms & Infrastructure
๐ก Hardware, Wireless & Field Projects
- PNWC Cyberdeck
- Hardware Testing
- Hardware Hacking
- Software-Defined Radio
- Wardriving
- uConsole
- Space Security
๐งฐ Assessment & Field Reference
๐ฆ Downloads & Project Resources
๐๏ธ Additional Topics