Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
aeondave/hardware-ctfMobile, firmware e hardware

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 instalações+3 em 7 dias39 EstrelasMITsincronizado há 10 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/hardware-ctf

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
AwQttAe6iA…YhFT55Cg==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote0a99bc37…d4f96325
0a99bc376e88…3d1cd4f963254 arquivos · ⁦10.2 KB⁩
VarreduraMédio2 achados
  • injection.no_confirmationreferences/debug-ports-and-firmware-extraction.md:81
  • Links para domínios externos
Ver a varredura completa
Fontegithub.com/AeonDave/malskill/tree/main/offensive-ctf/hardware-ctf@21cd568

Este item ainda não foi escrito no seu idioma, então aparece em 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 .sal files, 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

  1. Preserve evidence and identify artifact class: capture, firmware, board/interface, RF sample, side-channel dataset, or CAD/G-code.
  2. Lock physical assumptions: sample rate, voltage domain, channel order, idle level, clock, endian, bit order, modulation, architecture, and toolchain.
  3. Decode the transport before interpreting payloads: bus framing, packet boundaries, checksums, compression, filesystem, or symbol timing.
  4. Choose the narrowest tool path: protocol decoder, firmware extractor, disassembler, emulator, SDR flowgraph, side-channel statistic, or visualization.
  5. Validate by reconstructing an observable: secret bytes, image, waveform, register trace, firmware string, UART console output, HID path, RF message, or 3D geometry.
  6. Record every assumption that affects decoding so the proof can be replayed or corrected.

Technique integration

Load these as needed:

  • forensic-technique for evidence handling, carving, metadata, timelines, and PCAP/peripheral reconstruction.
  • reversing-technique for firmware, bootloaders, microcontroller binaries, and custom parsers.
  • wireless-technique for RF/SDR, Bluetooth, Wi-Fi-derived, or radio telemetry tasks.
  • network-technique for USB/Bluetooth/CAN PCAPs and protocol captures.
  • web-ctf when a hardware challenge exposes an HTTP or browser-based transceiver, status panel, or session-backed control plane around the decoded protocol.
  • arduino when a task requires real microcontroller wiring, sketches, Arduino CLI, PlatformIO, or board bring-up.
  • python-patterns and systematic-debugging for 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.

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosSimSim
Roda comandos no shellNãoNão
Usa a redeSimSim
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

  1. MédiaPrompt injection · injection.no_confirmationreferences/debug-ports-and-firmware-extraction.md:81
  2. InfoLink · Links para domínios externos

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.11.13-21cd56813 de nov. de 202621cd5680a99bc37Assinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login