hardware-ctf
Lab/CTF: hardware/embedded/RF challenges; Saleae/sigrok traces, UART/I2C/SPI/CAN/JTAG/SWD/USB/BLE/RF, firmware, side-channel data.
v2026.11.13-21cd5683 установки+3 за 7 дней39 ЗвездыMITсинхронизировано 10 часов назад
Установка
Ещё нет NotHoly CLI? Сначала установите её.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/hardware-ctfПишет в ~/.notholy/skills после проверки подписи и SHA-256.
ПодписьПодписано, ed25519
Пакет0a99bc37…d4f96325
0a99bc376e88…3d1cd4f963254 файла · 10.2 KBПроверкаСредний2 замечания
- injection.no_confirmationreferences/debug-ports-and-firmware-extraction.md:81
- Ссылки на внешние домены
Источникgithub.com/AeonDave/malskill/tree/main/offensive-ctf/hardware-ctf@21cd568
Эта запись еще не переведена на русский, поэтому показан текст на другом языке: English.
На странице
Solve hardware and embedded lab tasks by identifying the capture or device interface first, then decoding with timing, voltage, framing, and architecture assumptions made explicit.
When this skill applies
- Logic analyzer captures, Saleae
.salfiles, sigrok sessions, CSV edge traces, oscilloscope traces, audio captures of serial data, or display-signal samples. - UART, I2C, SPI, CAN, CANopen, JTAG, SWD, USB HID, USB MIDI, Bluetooth RFCOMM/BLE, RF/SDR, RFID/NFC, or peripheral PCAPs.
- Firmware images, SPI flash dumps, UEFI/BIOS blobs, bootloaders, microcontroller binaries, extracted filesystems, board photos, pinouts, schematics, CAD, G-code, or 3D-printing artifacts.
- Side-channel data such as power traces, timing traces, acoustic keyboard samples, LED Morse, or EM/RF measurements.
Operating model
- Preserve evidence and identify artifact class: capture, firmware, board/interface, RF sample, side-channel dataset, or CAD/G-code.
- Lock physical assumptions: sample rate, voltage domain, channel order, idle level, clock, endian, bit order, modulation, architecture, and toolchain.
- Decode the transport before interpreting payloads: bus framing, packet boundaries, checksums, compression, filesystem, or symbol timing.
- Choose the narrowest tool path: protocol decoder, firmware extractor, disassembler, emulator, SDR flowgraph, side-channel statistic, or visualization.
- Validate by reconstructing an observable: secret bytes, image, waveform, register trace, firmware string, UART console output, HID path, RF message, or 3D geometry.
- Record every assumption that affects decoding so the proof can be replayed or corrected.
Technique integration
Load these as needed:
forensic-techniquefor evidence handling, carving, metadata, timelines, and PCAP/peripheral reconstruction.reversing-techniquefor firmware, bootloaders, microcontroller binaries, and custom parsers.wireless-techniquefor RF/SDR, Bluetooth, Wi-Fi-derived, or radio telemetry tasks.network-techniquefor USB/Bluetooth/CAN PCAPs and protocol captures.web-ctfwhen a hardware challenge exposes an HTTP or browser-based transceiver, status panel, or session-backed control plane around the decoded protocol.arduinowhen a task requires real microcontroller wiring, sketches, Arduino CLI, PlatformIO, or board bring-up.python-patternsandsystematic-debuggingfor decoders, parsers, visualization, and reproducible notebooks/scripts.
Tool routing
- Logic/bus:
saleae-logic-2, sigrok/PulseView, sigrok-cli, logic2 automation, Python edge decoders, and protocol decoders. - Firmware:
binwalk,strings, dd, unsquashfs, UEFITool, chipsec, flashrom,ghidra,radare2,binaryninja, QEMU, and OpenOCD. - RF/SDR: GNU Radio, Universal Radio Hacker, rtl_433, inspectrum, spectrum tooling, numpy/scipy, and custom demodulators.
- Peripheral captures:
wireshark,tcpdump, usbmon,bluez, HID report parsers, MIDI decoders, and image/path reconstruction scripts. - Side-channel: numpy, scipy, pandas, matplotlib, correlation/DPA scripts, FFT/spectrogram tooling, and clustering/classification only after the signal is understood.
- CAD/G-code: slicer-aware parsers, zlib/heatshrink/QOI decoders, mesh viewers, coordinate projection, and metadata extraction.
Safety and scope gates
- Do not recommend wiring, flashing, or probing real hardware until voltage, ground, pin role, and target ownership are explicit.
- Prefer offline decoding over physical interaction when artifacts are sufficient.
- Avoid write operations through JTAG/SWD/SPI/flashrom unless an isolated lab target and recovery path are clear.
- Treat unknown pins as unsafe; identify power, ground, reset, boot, UART, and debug pins before connecting tools.
- For RF, follow local legal and lab constraints; passive analysis and replay in shielded or simulated environments are safer defaults.
Quick pivots
- Logic capture: infer sample rate, channels, idle levels, clock, start/stop bits, and bus decoder settings.
- UART: test baud, parity, stop bits, inversion, and line endings before parsing text.
- I2C/SPI: identify clock/data/chip-select, address or opcode patterns, and multi-byte endian.
- CAN: group arbitration IDs, infer periodic frames, counters, checksums, and signal scaling.
- JTAG/SWD: identify pins non-destructively, confirm chain/device ID, then dump or halt only in lab scope.
- Firmware: extract filesystem, identify architecture, search strings/configs, then reverse validation paths.
- RF/SDR: identify sample format, center frequency, symbol rate, modulation, framing, whitening, and checksum.
- Hybrid RF + web control plane: decode the burst offline first, then use UI state, session fields, or mission text as a control-plane oracle; re-decode each fresh capture instead of assuming a prior instance's exact bytes still apply.
- Side-channel: align traces, average noise, find leakage point, then validate recovered key/material independently.
Resources
- references/hardware-artifact-workflow.md — Load for capture, bus, firmware, RF, side-channel, fault-injection evidence or CAD/G-code triage.
- references/debug-ports-and-firmware-extraction.md — load for UART/JTAG/SWD/SPI/eMMC pivots, bootloader access, flash dumping, and recovery-first extraction.
- references/rf-and-sdr-decoding.md — load for IQ captures, SDR demodulation, BLE hopping analysis, and physical-layer validation before payload interpretation.
Файлы этой версии
references/317.9 KB
- debug-ports-and-firmware-extraction.md6.3 KB
- hardware-artifact-workflow.md8.5 KB
- rf-and-sdr-decoding.md3.2 KB
- SKILL.md5.9 KB
Права
| Право | Заявлено | Найдено проверкой |
|---|---|---|
| Читает файлы | Нет | Нет |
| Пишет файлы | Да | Да |
| Выполняет команды shell | Нет | Нет |
| Ходит в сеть | Да | Да |
| Использует коннекторы | Нет | Нет |
| Управляет браузером | Нет | Нет |
Замечания проверки
Проверено 13 нояб. 2026 г.
- СредняяPrompt injection · injection.no_confirmationreferences/debug-ports-and-firmware-extraction.md:81
- ИнфоСсылка · Ссылки на внешние домены
Чистая проверка снижает риск, но не доказывает, что пакет безопасен. Читайте то, что ставите.
| Версия | Опубликована | Коммит | SHA-256 | Подпись | Изменение прав |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | 13 нояб. 2026 г. | 21cd568 | 0a99bc37 | Подписана | – |
Ещё от AeonDave
Всё от этого издателяЕще в категории «Мобильные устройства, прошивки и железо»
Вся категорияСпрашивайте обо всём, что позволяет ваш скоуп.
Создайте аккаунт, пополните баланс и задайте первый вопрос в чате или в терминале.
- 1/3
Создайте аккаунт
Личный или для компании. Позже можно перейти на аккаунт компании без потери баланса и ключей.
ЛичныйКомпания - 2/3
Пополните баланс
Картой. Оплата за токены, без подписки.
$5.00минимальное пополнение - 3/3
Спрашивайте
В чате, или установите CLI и выполните notholy login в терминале.
$ notholy login