hardware-security
Discover and triage hardware debug interfaces (UART, JTAG, SWD) on an authorized embedded device — read boot logs, land a root console, interrupt the bootloader, and extract flash for offline analysis. Load when handed a physical device, PCB, or IoT/embedded target in scope, exposed test points or h
v2026.10.14-ee0e0c53 instalações+3 em 7 dias27 EstrelasMITsincronizado há 22 horas
Instalar
Ainda não tem a CLI da NotHoly? Instale primeiro.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/hardware-securityGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacote5985b2f2…13cef323
5985b2f2a079…f36313cef3231 arquivo · 2.8 KBVarreduraBaixo1 achado
- Links para domínios externos
Fontegithub.com/NoorQureshi/security-skills/tree/main/skills/hardware/hardware-security@ee0e0c5
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
When it applies
You have physical access to a device you own or are explicitly authorized to open — a router,
IoT gadget, embedded controller, or a board pulled from a larger system — and you need console
access or a firmware image. Hardware work is governed by the same envelope as everything else:
load tradecraft-scope-roe first and confirm the physical device and the teardown itself are in
scope.txt. Never open or probe a device that isn't yours or in writing.
Why it works
Vendors leave debug and factory-test interfaces on the board: a UART serial console for boot logs (often a root shell), and JTAG/SWD for chip-level debugging and memory readout. These ports bypass all software authentication on the running system — if you can electrically reach them and match the logic levels, the device talks to you. Bootloader consoles (U-Boot) additionally let you alter boot arguments or read flash before the OS locks anything down.
Method
- Open, photograph, label. Photograph both board sides before touching anything; note
silkscreen near pad clusters:
TX RX GND VCC(UART) andTDI TDO TCK TMS(JTAG),SWDIO/SWCLK(SWD). Mind ESD — ground yourself; default to read-only probing. - Identify the UART pinout with a multimeter, not guesses. Find GND (continuity to a shield or ground pour), VCC (stable rail at power-on), TX (pulses during boot — confirm with a logic analyzer if ambiguous), RX (floating/pulled line next to TX). Measure the logic level first — 1.8 V, 3.3 V, or 5 V — and match your adapter to it before connecting anything.
- Attach read-only first. Connect only GND + the board's TX to a USB-TTL adapter and watch the
boot log:
screen /dev/ttyUSB0 115200(orminicom). If the output is garbage, sweep common baud rates (9600/38400/57600/115200) until the log is legible; record the rate. Boot logs alone leak flash layout, kernel version, and often credentials. - Work the console. Many devices drop to a root shell with no password. Interrupt U-Boot at
the countdown (usually any key) and dump
printenv— note the environment, but do notsaveenvcasually: a wrong write bricks the boot. - Probe JTAG/SWD if UART is dead or locked. With a J-Link or CMSIS-DAP adapter under OpenOCD,
enumerate the chain and read the IDCODE:
openocd -f interface/jlink.cfg -f target/<chip>.cfg. A populated IDCODE means the debug port is live; an all-zeros/all-ones response means it's fused off or your wiring/level is wrong. - Extract flash for offline analysis. In-circuit SPI dumps with a cheap programmer:
flashrom -p ch341a_spi -r dump.bin(verify with a second dump and compare hashes). Immediately recordshasum -a 256 dump.binfor evidence integrity, then hand the image toreverse-eng-firmwarefor extraction and analysis; individual binaries go toreverse-eng-binary-triage. - Assess secure-boot/encrypted-flash feasibility non-destructively first (signed-image checks in the boot log, eFuse hints from JTAG behavior) before considering chip-off or glitching — those are destructive and need explicit sign-off.
Gotchas
- Wrong logic level kills ports. Connecting a 5 V adapter to a 1.8 V UART can destroy the SoC pins. Measure first; use a level shifter when in doubt.
- Garbage output ≠ no console — it's usually the wrong baud rate. Sweep before concluding the port is mute. Truly silent UARTs may be disabled in firmware; fall back to JTAG.
- TX/RX are named from the board's perspective — your adapter's RX listens to the board's TX. Read-only logging only needs GND + board TX.
- A locked JTAG (empty IDCODE) is a finding too — it tells you the vendor spent effort on debug-lockout, which shapes the rest of the assessment (chip-off vs. software attack surface).
- Every write is a bricking risk.
saveenv, flash erase/program, and eFuse operations are one-way doors; get explicit approval and a verified dump before any of them.
Verify success
You have a labeled pinout photo with measured logic levels, the recorded baud rate, and at least
one of: a working console (shell or U-Boot prompt), a live JTAG/SWD chain (valid IDCODE), or a
SHA256-hashed flash dump ready for reverse-eng-firmware. If everything is locked, you can state
precisely which interfaces exist and how each is disabled — that negative result is deliverable.
References
OpenOCD and flashrom documentation; reverse-eng-firmware for what to do with the dump.
Portions adapted from reverse-skill by zhaoxuya520, MIT License.
Arquivos desta versão
- SKILL.md5.3 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Não | Não |
| Grava arquivos | Não | Não |
| Roda comandos no shell | Não | Não |
| Usa a rede | Sim | Sim |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
- 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ão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 de nov. de 2026 | ee0e0c5 | 5985b2f2 | Assinada | – |
Mais de NoorQureshi
Tudo deste publicadorMais em Mobile, firmware e hardware
Ver a categoriaPergunte 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/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login