Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/uart-consoleMobile, firmware and hardware

uart-console

⁨Identification, connection, and exploitation of UART serial consoles (U-Boot/Barebox interrupt, bootargs patching) during hardware assessments.⁩

v2026.11.13-21cd5683 installs+3 in 7 days39 Starssynced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/uart-console

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
0UFcSicHSD…xdVbGACg==The CLI checks the SHA-256 and the signature before it writes a file.
Package288690fe…b218d111
288690fe3121…7355b218d1111 file · ⁦1.2 KB⁩
ScanMedium1 finding
  • No license found
See the full scan
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-hardware/uart-console@21cd568

Use when physical access is available, and you need an interactive root shell without desoldering chips or risking firmware corruption.

1. Pin identification

  • Visual: Look for 3-4 unpopulated through-holes or test pads near the SoC.
  • Multimeter:
    1. GND: 0 V (continuity with shielding).
    2. VCC: 3.3 V or 5 V (constant).
    3. TX: Idle HIGH (3.3 V), fluctuates during boot.
    4. RX: High-impedance (floats to ~0 V or pull-up).
  • JTAGulator: Use UART scan capability if pads are unlabeled/dense.

2. Connection

Rule: Do NOT connect VCC if the device is self-powered. This causes voltage collision.

  • Connect: GND → GND, RX → TX_pad, TX → RX_pad.
bash
# Try standard baud rates: 115200, 57600, 38400, 19200, 9600
screen /dev/ttyUSB0 115200
# or
minicom -D /dev/ttyUSB0 -b 115200

If output is garbled, cycle through baud rates. Check logic analyzer for precise rate if needed.

3. Bootloader exploitation (U-Boot)

Monitor output closely on power-on.

  • Prompt: Hit any key to stop autoboot. Press immediately.

Key U-Boot commands:

bash
printenv         # Dump environment variables (credentials, boot paths, keys)
md 0x80000000    # Hex dump memory (hunt for loaded keys/passwords)
boot             # Resume boot process

Drop to shell (root init bypass):

bash
# Replace normal init with a shell to bypass authentication
setenv bootargs 'console=ttyS0,115200 root=/dev/mtdblock2 init=/bin/sh'
boot

4. Secure boot bypass patterns

If U-Boot enforces verified boot (CONFIG_SECUREBOOT):

  1. Read signing keys from NAND/SPI mapping (sometimes unprotected).
  2. Patch U-Boot env locally to drop CONFIG_SECUREBOOT (requires SPI write).
  3. Voltage glitching on SoC VCC rail exactly during signature verification branching.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsYesYes
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumLicense · No license found

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.11.13-21cd568Nov 13, 202621cd568288690feSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login